Internet Architecture, E-Business and Digital Platforms

Introduction

The internet is not merely a communication medium; it is a global socio-technical infrastructure on which firms design business models, deliver services, collect data and coordinate markets. Modern organisations depend on internet service providers, domain-name systems, web technologies, cloud services and digital-payment infrastructures. At the same time, digital platforms have transformed competition by connecting multiple groups—such as buyers and sellers, passengers and drivers, or merchants and customers—within a common technological and commercial environment.

For MBA managers, understanding this environment requires more than learning technical vocabulary. Managers must evaluate how internet architecture affects service quality, cost, cybersecurity, scalability, customer experience, regulation and competitive advantage. This chapter therefore connects the technical structure of the internet with e-business, e-commerce, fintech, marketplaces and platform strategy.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain the roles of internet service providers, DNS, web infrastructure and cloud services.
2. Distinguish e-business from e-commerce and identify major digital business processes.
3. Analyse digital platforms, marketplaces and network effects.
4. Explain digital-payment and fintech structures, risks and governance requirements.
5. Evaluate cybersecurity, privacy and trust issues in online business.
6. Apply platform and e-commerce concepts to a managerial case.

1. Internet Structure: From User to Global Service

1.1 The layered nature of the internet

The internet is a network of interconnected networks. No single organisation owns the entire internet. Instead, it consists of household and organisational networks, access networks, regional networks, backbone networks, data centres, content-delivery networks and exchange points. Communication is divided into packets, which are routed across networks using standard protocols.

A simplified service path is:

User device → local network/router → ISP access network → internet backbone or exchange point → hosting or cloud infrastructure → application service.

The separation between layers is strategically important. A business may own its application and customer data while renting connectivity, servers and security services from other providers. Failures can therefore arise at several points: local access, DNS resolution, routing, hosting, software, payment processing or identity management.

1.2 Internet Service Providers (ISPs)

An Internet Service Provider supplies access to the internet. ISPs serve households, businesses, public institutions and other network operators. Their services may include broadband access, mobile data, leased lines, IP address allocation, domain registration, email hosting, virtual private networks and managed security.

ISPs perform several functions:

• Access: They connect users to the wider internet through fibre, cable, wireless, satellite or mobile networks.
• Routing: They use routers and routing protocols to forward packets toward their destinations.
• Addressing: They provide or coordinate Internet Protocol addresses, which identify network interfaces.
• Peering and transit: ISPs exchange traffic directly with other networks or pay larger networks for transit.
• Operational support: They monitor availability, manage congestion and respond to faults or abuse.
• Security and policy enforcement: They may filter malicious traffic, block illegal content under applicable law, and respond to lawful requests.

For organisations, the choice of ISP is a business-continuity decision, not merely a purchasing decision. Relevant criteria include bandwidth, latency, reliability, service-level agreements, redundancy, geographic coverage, technical support, data protection and price.

Bandwidth measures the volume of data that can theoretically be transferred per unit of time, usually in bits per second. Latency measures delay, commonly in milliseconds. A video-streaming service needs high capacity, while an algorithmic trading or interactive gaming service is particularly sensitive to latency. Reliability is often represented by availability. If a service is available for 8,760 hours in a year and unavailable for 8.76 hours, its availability is approximately 99.9%:

This calculation assumes that the measurement period and downtime definition are agreed in advance. A high availability percentage does not guarantee good performance if latency or packet loss is excessive.

1.3 Domain Name System (DNS)

Computers communicate using numerical IP addresses, but people prefer memorable names such as example.com. The Domain Name System translates domain names into IP addresses and supports other records used by internet services.

DNS is a distributed hierarchical database. Important components include:

• Root servers: Direct queries toward top-level domain authorities.
• Top-level domain servers: Manage domains such as .com, .org and country-code domains.
• Authoritative name servers: Hold the official records for a domain.
• Recursive resolvers: Receive a user’s request and query other DNS servers when the answer is not already cached.
• DNS records: Include A or AAAA records for addresses, MX records for email routing, CNAME records for aliases and TXT records for verification or security policies.

When a user enters a web address, a resolver generally checks its cache before querying higher-level servers. The time for which a response may be cached is controlled by the time-to-live value. Caching improves speed and reduces DNS traffic, but changes to records may not take effect everywhere immediately.

DNS is essential to business continuity. Incorrect records can redirect customers, disable email or make a website unreachable. DNS attacks may include cache poisoning, domain hijacking and distributed denial-of-service attacks against authoritative services. Organisations should use registrar controls, multi-factor authentication, domain-locking mechanisms, DNS monitoring and DNS Security Extensions where appropriate.

1.4 The World Wide Web

The World Wide Web is an application system that operates over the internet. It commonly uses browsers, web servers and protocols such as HTTP or HTTPS. A web application normally contains:

1. Client layer: Browser or mobile interface that presents content and collects input.
2. Application layer: Business logic, authentication, product search, order processing and workflow.
3. Data layer: Databases, object storage, logs and analytical repositories.
4. Integration layer: APIs connecting payments, logistics, identity, marketing and external partners.

HTTPS uses encryption and authentication through Transport Layer Security. It protects data in transit and helps users verify that they are communicating with the intended domain. HTTPS does not, however, guarantee that a website is honest, that its database is secure or that a user’s device is free from malware.

Web architectures may be monolithic, service-oriented or microservice-based. A monolithic application deploys many functions as one unit and can be simpler to operate initially. A microservice architecture divides functions into independently deployable services, potentially improving scalability and team autonomy but increasing operational complexity, monitoring requirements and inter-service security risks.

2. Cloud-Service Structures

Cloud computing provides on-demand access to computing resources over a network, usually with elastic capacity and usage-based charging. The principal service models are:

Cloud deployment may be public, private, hybrid or multi-cloud. Public cloud can provide rapid scaling and global reach. Private cloud may offer greater organisational control. Hybrid approaches combine environments, while multi-cloud strategies use more than one provider to reduce dependence or meet regulatory and technical requirements.

Cloud architecture commonly includes virtual machines or containers, load balancers, databases, object storage, identity services, monitoring and automated deployment tools. A load balancer distributes requests across multiple servers. Elasticity enables capacity to increase during a promotion and decrease afterward. These advantages support e-commerce, but they do not eliminate managerial responsibility. Customers remain responsible for configuration, access control, data classification, regulatory compliance and application security under the shared-responsibility model.

A cloud decision should assess total cost, workload volatility, data location, portability, exit costs, resilience, supplier concentration and service-level commitments. Low initial cost can be misleading if data transfer, premium support, idle resources or proprietary interfaces create substantial long-term expense.

3. E-Business and E-Commerce

3.1 E-business versus e-commerce

E-commerce is the buying and selling of goods or services through electronic networks. It includes online ordering, digital product delivery, electronic invoicing and online payment.

E-business is broader. It includes e-commerce as well as digitally enabled procurement, customer relationship management, supply-chain coordination, human resources, online service delivery, analytics and internal collaboration. A manufacturer using an online supplier portal and real-time inventory integration is conducting e-business even when the final sale occurs through a physical channel.

Common e-commerce categories include:

• Business-to-consumer (B2C): A retailer sells directly to individual customers.
• Business-to-business (B2B): A firm sells to another organisation.
• Consumer-to-consumer (C2C): Individuals trade through a marketplace.
• Consumer-to-business (C2B): Individuals provide value to firms, as in freelance services or influencer content.
• Business-to-government (B2G): Firms supply public bodies through digital procurement systems.

An e-commerce value chain includes customer acquisition, product discovery, identity and authentication, catalogue management, pricing, shopping-cart management, payment authorisation, fulfilment, delivery, customer support, returns and post-sale analytics. Competitive advantage may arise from price, assortment, convenience, personalisation, trust, delivery speed or ecosystem integration.

3.2 Digital customer journeys and business metrics

The digital customer journey may be analysed as a sequence of awareness, consideration, acquisition, conversion, fulfilment, retention and advocacy. Managers should distinguish traffic from value. A website may receive substantial traffic but generate little profit if conversion, average order value or retention is weak.

Useful metrics include conversion rate, cart-abandonment rate, customer-acquisition cost, customer lifetime value, fulfilment cost, return rate and contribution margin. A basic conversion rate is:

The measure is meaningful only when “qualified visit” and transaction definitions are consistent. Customer lifetime value is not a universal single formula; a simplified contribution approach is:

This approximation assumes stable contribution and retention and excludes discounting, changing behaviour and unusual service costs. For strategic decisions, managers should use cohort analysis and, where appropriate, discounted cash-flow methods.

4. Digital Platforms and Marketplaces

4.1 Platform business models

A digital platform facilitates interactions between two or more participant groups. Examples include buyers and sellers, hosts and guests, drivers and passengers, advertisers and audiences, or app developers and users. The platform typically provides rules, search, identity, matching, payment, reputation systems and dispute resolution.

A pipeline business creates value through a relatively linear sequence: inputs are transformed into products and distributed to customers. A platform business creates value by enabling interactions among participants. It may not own the principal inventory. An accommodation marketplace, for example, can coordinate rooms supplied by hosts without owning hotels.

Platform design involves several strategic choices:

• Which participant groups should be served?
• Which side should be subsidised or acquired first?
• How should participants be verified and ranked?
• What rules prevent fraud and low-quality behaviour?
• How should revenue be generated—commission, subscription, advertising, listing fees or a combination?
• How open should the platform be to outside developers and sellers?

4.2 Network effects

A network effect occurs when the value of a service changes as participation changes. Direct network effects arise when users benefit from more users on the same side, as with communication applications. Indirect or cross-side network effects arise when growth on one side increases value for another side, as when more sellers attract buyers and more buyers attract sellers.

Network effects can produce rapid growth, economies of scale and market concentration. They can also create congestion, fraud, exclusion and dependence on a dominant platform. Network effects should not be confused with ordinary economies of scale. Economies of scale reduce average cost as output increases; network effects increase user value as participation changes.

A platform may face a “chicken-and-egg” problem: buyers want many sellers, while sellers want many buyers. Common solutions include subsidising one side, recruiting anchor participants, guaranteeing transactions, restricting initial geographic scope or integrating complementary services.

Platform governance is as important as technology. Rules concerning ranking, commissions, content moderation, data access, seller suspension, refunds and algorithmic recommendations shape the distribution of value and power. Excessive extraction may cause participants to multi-home—use several platforms—or leave altogether.

5. Digital Payments and Fintech

Fintech applies software, data and network technologies to financial services. In e-commerce, fintech supports payment acceptance, digital wallets, account-to-account transfers, buy-now-pay-later products, fraud detection, lending, insurance and identity verification.

A card or wallet transaction generally involves the customer, merchant, payment gateway, payment processor, acquiring institution, card scheme or payment network, and issuing institution. The process may include:

1. Customer authentication and payment initiation.
2. Authorisation by the issuing institution.
3. Clearing of transaction information among participants.
4. Settlement and transfer of funds.
5. Reconciliation, refunds and dispute handling.

Digital payments provide convenience and speed but introduce risks. These include account takeover, payment fraud, false chargebacks, privacy loss, operational outages, liquidity problems and dependence on a small number of providers. Managers should assess authentication, tokenisation, encryption, transaction monitoring, segregation of duties and reconciliation controls.

Strong customer authentication can combine knowledge, possession and inherence factors, although implementation depends on law and payment context. Tokenisation replaces sensitive payment credentials with a substitute token, reducing exposure if merchants do not store the original credential. Encryption protects data while it is transmitted or stored, but access controls and key management remain essential.

Fintech also raises questions about financial inclusion and exclusion. Digital credit can extend access to finance, but automated scoring may reproduce historical discrimination or penalise people with limited digital records. Explainability, fairness testing, human review, complaint mechanisms and responsible lending are therefore managerial and ethical requirements.

6. E-Business Cybersecurity and Trust

Cybersecurity protects the confidentiality, integrity and availability of information and systems. E-business environments also require authenticity, accountability, privacy and resilience.

Major threats include phishing, credential theft, ransomware, web-application vulnerabilities, insecure APIs, supply-chain compromise, insider misuse, denial-of-service attacks and fraudulent merchants. A platform’s attack surface grows as it adds sellers, applications, integrations and customer data.

A practical cybersecurity programme should include:

• Asset inventories and data classification.
• Strong identity and access management, including least privilege and multi-factor authentication.
• Secure software development and vulnerability testing.
• Network segmentation and endpoint protection.
• Encryption in transit and at rest.
• Logging, monitoring and anomaly detection.
• Backups tested through restoration exercises.
• Incident-response plans with defined responsibilities.
• Supplier and cloud-risk assessments.
• Staff training and phishing simulations.
• Privacy-by-design and retention limits.

Cybersecurity is a risk-management problem rather than a one-time technical purchase. A simple expected-loss model is:

The model is useful for comparing controls but is only an approximation. Probability estimates may be uncertain, impacts may be nonlinear, and reputational or regulatory consequences may be difficult to quantify.

Trust in e-commerce is created through reliable fulfilment, transparent prices, authentic reviews, clear returns, secure payment, privacy protection and effective dispute resolution. A technically secure website can still lose trust if it uses deceptive design, hides fees or manipulates customers into unwanted subscriptions.

7. Regulation, Ethics and Governance

Digital business operates across jurisdictions. Relevant obligations may concern privacy, consumer protection, electronic contracts, accessibility, taxation, payments, anti-money-laundering controls, competition and cybersecurity incident reporting. Managers must identify applicable laws rather than assuming that the location of a server determines all legal obligations.

Important governance principles include data minimisation, purpose limitation, informed consent where required, user access and correction rights, retention controls and responsible cross-border transfer. Platform firms should document ranking and moderation processes, provide fair appeals, control conflicts of interest and monitor discriminatory outcomes.

Competition authorities increasingly examine self-preferencing, exclusive arrangements, tying, unfair access conditions and the acquisition of potential competitors. A large user base does not excuse harmful conduct. Platform success must be evaluated alongside consumer welfare, supplier welfare, innovation and market contestability.

Artificial intelligence is now used for recommendation, search ranking, fraud detection, customer service and dynamic pricing. Its benefits include speed and personalisation, but risks include bias, opaque decisions, privacy intrusion, model drift and adversarial manipulation. Human oversight, performance monitoring, audit trails and clear escalation procedures are essential in high-impact decisions.

8. Applied Case: GreenBasket Digital Marketplace

Background

GreenBasket is an illustrative online marketplace connecting urban consumers with small local food producers. It offers product discovery, digital payment, home delivery and subscription boxes. Initially, GreenBasket operated a simple website and manually processed orders.

Problem

Growth produced slow page responses, payment failures, duplicate orders, fraudulent seller accounts and inconsistent product quality. Producers complained that ranking algorithms favoured large suppliers. Customers abandoned carts when delivery fees appeared late in the process.

Analysis

The firm’s problems were interconnected. Its single application and database created a bottleneck during promotional events. DNS and hosting were managed by one small supplier with weak access controls. Payment credentials were handled inconsistently. The platform had cross-side network effects, but poor supplier verification damaged consumer trust. Ranking rules encouraged paid visibility without clearly disclosing it.

Approach and solution

GreenBasket adopted a managed cloud architecture with separate catalogue, order, payment and notification services. A content-delivery network improved delivery of static content, while database replication and automated backups improved resilience. The company introduced multi-factor authentication for administrators, role-based access, tokenised payments and continuous monitoring.

It redesigned onboarding using business verification, product standards and periodic audits. Ranking was changed to combine relevance, availability, delivery performance, customer feedback and clearly labelled paid placement. Delivery fees were displayed before payment confirmation. A dispute process gave both buyers and sellers access to evidence and appeal.

The company also used staged geographic expansion rather than attempting national coverage immediately. It subsidised producer onboarding in two cities, created minimum service standards and measured repeat purchases rather than registrations alone.

Outcome

The redesigned system reduced operational bottlenecks and made failures easier to isolate. Transparent ranking and clearer fees improved trust, while supplier standards reduced complaints. The firm accepted somewhat slower expansion in exchange for stronger quality and retention.

Learning points

1. Technical scalability must be matched by governance scalability.
2. Network effects are valuable only when participation produces reliable quality.
3. Payment security and customer trust are strategic capabilities.
4. Platform rules distribute economic value and therefore require ethical justification.
5. Metrics should include retention, contribution margin, disputes and supplier health—not merely user growth.

9. Managerial Framework for Digital-Platform Decisions

Managers evaluating an internet-based business can use the following sequence:

1. Define the value proposition: What problem is solved, for whom and with what evidence?
2. Map the architecture: Identify ISP, DNS, web, cloud, data, payment and partner dependencies.
3. Assess economics: Estimate acquisition cost, contribution margin, fulfilment expense, retention and platform commissions.
4. Analyse network effects: Determine which side benefits from growth and how initial participation will be created.
5. Design trust mechanisms: Include verification, reviews, payment protection, privacy and dispute resolution.
6. Evaluate resilience: Test redundancy, recovery time, supplier concentration and incident response.
7. Review legal and ethical exposure: Examine privacy, competition, consumer protection, accessibility and algorithmic fairness.
8. Measure outcomes: Use technical, financial, customer, supplier and social indicators.

A platform should not pursue growth at any cost. Sustainable digital advantage depends on reliable infrastructure, credible governance, positive participant economics and the ability to adapt as regulation and technology evolve.

Contemporary Developments and Future Direction

Current developments include edge computing, embedded finance, open banking, digital identity, application-programming interfaces, real-time payments, serverless computing and AI-assisted operations. Edge computing can reduce latency by processing data closer to users. Open banking can enable authorised third parties to access financial data or initiate payments under regulated arrangements. Embedded finance places payment, credit or insurance inside non-financial applications.

These developments create opportunities but also increase integration complexity and systemic dependence. Managers should favour interoperable standards where practical, maintain exit strategies, test concentration risk and ensure that innovation does not weaken consent, security or accountability.

Chapter Summary

The internet is a network of interconnected networks supported by ISPs, routing systems, DNS, web servers, cloud infrastructure and application services. ISPs provide access, routing and operational connectivity, while DNS translates human-readable domain names into technical destinations. Web and cloud architectures allow firms to deliver scalable digital services, but cloud adoption does not remove the customer’s responsibility for security, governance and continuity.

E-business includes all digitally enabled organisational activities; e-commerce specifically concerns electronic buying and selling. Digital platforms create value by enabling interactions among multiple participant groups. Marketplaces depend on trust, matching, governance, payment systems and network effects. Direct and cross-side network effects can accelerate growth but may also create concentration, dependency and exclusion.

Fintech and digital payments improve convenience and enable new business models, but require authentication, tokenisation, fraud management, reconciliation and regulatory oversight. Cybersecurity must protect confidentiality, integrity and availability while also supporting privacy, resilience and accountability. Finally, sustainable platform strategy combines sound architecture, participant welfare, transparent governance, responsible data use and measurable economic value.

Key Terms

ISP: An organisation that provides access to internet networks and related services.

DNS: A distributed system that translates domain names into network addresses and service records.

IP address: A numerical identifier assigned to a network interface.

HTTP/HTTPS: Web communication protocols, with HTTPS adding encryption and authentication through TLS.

Cloud computing: On-demand access to shared computing resources over a network.

IaaS: Cloud provision of infrastructure such as virtual servers, storage and networks.

PaaS: Cloud provision of an application-development and runtime environment.

SaaS: Delivery of a complete software application through a network.

E-business: Digitally enabled business processes, transactions and organisational activities.

E-commerce: Electronic buying and selling of goods or services.

Digital platform: A system that enables interactions among two or more participant groups.

Marketplace: A platform that connects buyers and sellers.

Network effect: A change in service value associated with changes in participation.

Cross-side network effect: A network effect in which growth on one participant side affects value for another side.

Fintech: Technology-enabled innovation and delivery in financial services.

Tokenisation: Replacement of sensitive data with a substitute token.

Multi-factor authentication: Authentication using two or more distinct factor categories.

Cloud shared responsibility: The principle that provider and customer divide security and operational responsibilities.

Platform governance: Rules and mechanisms controlling participation, ranking, access, conduct and disputes.

Conversion rate: The percentage of qualified visits that result in a defined transaction.

Review Questions

5 Short Answer Questions

1. What functions does an ISP perform for a business customer?
2. Why is DNS important to e-commerce continuity?
3. Distinguish e-business from e-commerce.
4. What is a cross-side network effect?
5. How does tokenisation support digital-payment security?

5 Long Answer Questions

1. Explain the principal layers of a web-based business architecture and discuss their managerial significance.
2. Compare IaaS, PaaS and SaaS, including the responsibilities retained by the customer.
3. Analyse how marketplaces solve the chicken-and-egg problem.
4. Discuss the cybersecurity controls required by an online platform.
5. Explain how platform governance influences trust, competition and participant welfare.

3 Analytical / Application Questions

1. A retailer experiences slow performance during promotions, payment failures and repeated DNS outages. Diagnose the likely architectural weaknesses and recommend a phased improvement plan.
2. Design a launch strategy for a two-sided marketplace connecting independent tutors with students. Identify the subsidised side, trust mechanisms, revenue model and measures of network-effect success.
3. Evaluate an AI-based lending feature embedded in an e-commerce application. Analyse its commercial benefits, privacy and fairness risks, governance controls and regulatory questions.

Multiple Choice Questions with Answers

Question 1

Which function is primarily performed by the DNS?

A. Encrypting all data stored in a cloud database

B. Translating domain names into network addresses and service records

C. Authorising every credit-card transaction

D. Providing physical fibre connections to homes

Correct Answer: B. Translating domain names into network addresses and service records

Question 2

Which statement best distinguishes e-business from e-commerce?

A. E-business includes digitally enabled internal and external processes, whereas e-commerce focuses on electronic buying and selling

B. E-commerce includes all internal collaboration, whereas e-business only concerns retail sales

C. E-business can occur only through mobile applications

D. There is no meaningful distinction between the two concepts

Correct Answer: A. E-business includes digitally enabled internal and external processes, whereas e-commerce focuses on electronic buying and selling

Question 3

Which cloud model gives the customer the greatest responsibility for operating systems and applications?

A. Software as a Service

B. Platform as a Service

C. Infrastructure as a Service

D. Managed content delivery

Correct Answer: C. Infrastructure as a Service

Question 4

A platform becomes more valuable to buyers as the number of sellers increases. This is an example of:

A. A direct network effect only

B. A cross-side network effect

C. A reduction in bandwidth

D. A monolithic architecture

Correct Answer: B. A cross-side network effect

Question 5

Which control replaces sensitive payment credentials with a substitute value?

A. Tokenisation

B. DNS caching

C. Load balancing

D. Data deduplication

Correct Answer: A. Tokenisation

Question 6

A website receives 20,000 qualified visits and records 800 completed transactions. What is its conversion rate?

A. 2%

B. 4%

C. 8%

D. 25%

Correct Answer: B. 4%

Question 7

Which statement about HTTPS is correct?

A. It guarantees that every website using it is legitimate

B. It encrypts data in transit and supports authentication of the domain connection

C. It removes the need for access controls in the application

D. It prevents all malware from reaching a user’s device

Correct Answer: B. It encrypts data in transit and supports authentication of the domain connection

Question 8

Why might a platform subsidise one participant group during its launch?

A. To eliminate the need for governance

B. To create initial participation and stimulate cross-side network effects

C. To ensure that no participant can multi-home

D. To replace all cybersecurity controls

Correct Answer: B. To create initial participation and stimulate cross-side network effects

Question 9

Under the shared-responsibility model of cloud computing, which statement is most accurate?

A. The cloud provider is always responsible for every customer configuration

B. The customer has no responsibility for data or access controls

C. Provider and customer divide responsibilities according to the service and deployment model

D. Responsibility is transferred entirely to the internet service provider

Correct Answer: C. Provider and customer divide responsibilities according to the service and deployment model

Question 10

Which metric is most directly concerned with the proportion of visits producing transactions?

A. Latency

B. Availability

C. Conversion rate

D. Bandwidth

Correct Answer: C. Conversion rate