Business Data Communication and NetworkingUnit 109 min read
Business Networks: Models, Security & Strategic Use
Unit 10 of Business Data Communication and Networking explores how organizations leverage networks for operations, security, and competitive advantage—covering network architectures, security frameworks, cloud adoption, and real-world case studies like Ncell’s IoT or Daraz’s logistics.
TAKEAWAYS:
- Business networks integrate hardware, software, and policies to optimize operations, security, and scalability.
- Network architectures (client-server, peer-to-peer, cloud) determine efficiency, cost, and fault tolerance.
- Security threats (DDoS, phishing, malware) require layered defenses like firewalls, encryption, and access controls.
- Cloud computing (SaaS, PaaS, IaaS) enables cost-effective scalability but demands compliance with GDPR/nepali data laws.
- Case studies (e.g., Nabil Bank’s ATM network, Daraz’s supply chain) show how theory applies to real-world challenges.
1. Business Network Models and Their Applications
Businesses deploy networks to connect employees, customers, and systems. The choice of model depends on cost, scalability, and security needs.
A. Network Architectures
Three primary architectures dominate business networks:
graph TD
root((Business Network Architectures))
Client-Server["Centralized
(e.g., bank servers)"]
P2P["Decentralized
(e.g., file sharing)"]
Hybrid["Combination
(e.g., cloud + local)"]
root --> Client-Server
root --> P2P
root --> Hybrid
Client-Server -->|"Example"| Ncell["Ncell billing"]
Client-Server -->|"Risk"| SinglePoint["Single point of failure"]
P2P -->|"Example"| Govt["Local govt file sharing"]
P2P -->|"Risk"| Security["Less secure"]
Hybrid -->|"Example"| Daraz["Cloud + warehouse"]
Hybrid -->|"Advantage"| Balance["Cost/control balance"]Network architectures with real-world Nepali examples and trade-offsWorked Example: Nabil Bank’s ATM Network
- Model: Client-server (ATMs as clients, central bank servers).
- Why? Centralized fraud detection and transaction logging.
- Challenge: High latency during peak hours → Solution: Load balancers distribute traffic.
B. Network Topologies in Business
Topologies define how devices connect. Common ones:
| Topology | Description | Business Use Case | Pros | Cons |
|---|---|---|---|---|
| Star | All devices connect to a central hub. | Corporate offices (e.g., Himalayan Java HQ) | Easy to manage, fault isolation | Single hub failure = network down |
| Mesh | Every device connects to others. | Disaster recovery sites (e.g., NTC backup centers) | Redundant paths, high reliability | High cost, complex setup |
| Bus | Single shared cable (legacy). | Small retail POS systems (e.g., local kirana shops) | Low cost | Single cable failure = all down |
| Ring | Devices in a closed loop. | Token-ring networks (rare today) | Predictable data flow | Slow to add/remove nodes |
Real-World Tie-In: Pathao’s Driver App
- Topology: Star (drivers connect to Pathao’s central server).
- Why? Real-time GPS updates and payment processing require low-latency central coordination.
2. Network Security in Business
Security breaches cost businesses millions (e.g., Nepal’s Rs. 200M+ lost to cybercrime in 2023). Key threats and defenses:
A. Common Threats
flowchart TD A["Security Threats"] --> B["Malware"] A --> C["Phishing"] A --> D["DDoS Attacks"] A --> E["Insider Threats"] B --> B1["Ransomware (e.g., eSewa hack 2022)"] C --> C1["Fake invoices (e.g., Daraz seller scams)"] D --> D1["Website downtime (e.g., NEPSE trading halts)"] E --> E1["Disgruntled employees (e.g., bank fraud)"]
B. Security Frameworks
Businesses use defense-in-depth:
| Layer | Tool/Technique | Example in Nepal |
|---|---|---|
| Physical | Biometric access, CCTV | Nabil Bank’s vaults, NTC data centers |
| Network | Firewalls, IDS/IPS | Daraz’s web application firewall |
| Application | Encryption (SSL/TLS), MFA | eSewa’s 2FA for transactions |
| Data | Backup, hashing | Ncell’s daily encrypted customer data backups |
Worked Example: eSewa’s Security Breach (2022)
- Threat: SQL injection → Impact: Rs. 20M stolen.
- Fix: Implemented WAF (Web Application Firewall) + rate limiting to block brute-force attacks.
3. Cloud Computing in Business
Cloud adoption in Nepal grew 300% in 5 years (2018–2023). Models:
graph TD
root((Cloud Models))
SaaS["SaaS: Google Workspace
(Small businesses)"]
PaaS["PaaS: Heroku
(Khalti APIs)"]
IaaS["IaaS: AWS EC2
(Daraz hosting)"]
root --> SaaS
root --> PaaS
root --> IaaSColor-coded cloud models with Nepali business applicationsComparison Table: Cloud vs. On-Premises
| Factor | Cloud (e.g., AWS, Nepal Cloud) | On-Premises (e.g., NTC’s old servers) |
|---|---|---|
| Cost | Pay-as-you-go (scalable) | High upfront hardware/software costs |
| Maintenance | Provider’s responsibility | IT team’s burden |
| Scalability | Instant (e.g., Daraz Black Friday) | Manual upgrades (slow) |
| Security | Shared responsibility model | Full control but risk of human error |
| Downtime Risk | Provider SLA (e.g., 99.9% uptime) | Depends on local power/internet |
Real-World Tie-In: Khalti’s Cloud Strategy
- Why Cloud? Handles 500K+ transactions/day without overloading local servers.
- Model: SaaS (for merchants) + IaaS (for transaction processing).
- Challenge: GDPR compliance for Nepali users’ data → Solution: Data stored in Singapore (low-latency) with encrypted backups in Nepal.
4. Network Performance and Optimization
Businesses optimize networks to reduce latency, improve uptime, and cut costs.
A. Key Metrics
B. Optimization Techniques
| Technique | How It Works | Example |
|---|---|---|
| Load Balancing | Distributes traffic across servers. | Ncell’s SMS gateway during festivals |
| Caching | Stores frequent data locally. | Daraz’s CDN for product images |
| QoS (Quality of Service) | Prioritizes critical traffic. | Bank ATMs get priority over email in Nabil Bank’s network |
Worked Example: Kathmandu Traffic vs. Network Traffic
- Problem: During Dashain, NTC’s network slows due to high data usage (video calls, downloads).
- Solution:
- Traffic shaping: Limit non-critical traffic (e.g., torrents).
- CDN: Cache popular content (e.g., festival greetings) closer to users.
5. Case Study: Daraz’s Network-Driven Logistics
Challenge: Deliver 100K+ orders/month with 95% on-time rate. Solution:
- Hybrid Network:
- Cloud (AWS): Order processing, inventory.
- Local Servers: Warehouse automation (RFID tracking).
- Security:
- End-to-end encryption for payment data.
- DDoS protection during sales (e.g., 11.11).
- Performance:
- Edge computing: Faster delivery route calculations.
6. Exam Tip: How This Unit Is Tested
Theory Questions (30%):
- Define client-server vs. P2P architectures.
- Explain firewall vs. IDS (difference and use cases).
- Compare SaaS vs. IaaS with Nepali examples.
Scenario-Based (40%):
- "Nabil Bank’s ATM network uses a star topology. If the central server fails, how would you improve reliability?" Answer: Add redundant servers + load balancers.
- "eSewa was hacked via SQL injection. Suggest 3 security controls." Answer: WAF, input validation, MFA.
Case Analysis (30%):
- Analyze Pathao’s driver app network (topology, security, scalability).
- Critique a local business’s network (e.g., "Why does a kirana shop use a bus topology?").
Common Pitfalls:
- Ignoring real-world examples: Always tie answers to Nepali companies (e.g., Ncell, Daraz, banks).
- Overcomplicating: For cloud models, stick to SaaS/PaaS/IaaS—no need for sub-layers.
- Security: Remember defense-in-depth (layered approach).
Final Visual Summary:
Based on the TU BITM syllabus for Business Data Communication and Networking (IT240), unit 10.
Discussion
Loading…