Design Questions

Q1. How will you design a LAN for 30 users in a college lab.
Ans: Designing a Local Area Network (LAN) for a college lab with 30 users requires careful
planning to ensure efficient connectivity, security, and ease of management. Here’s how you
could approach it:
1. Determine Network Requirements
 Number of devices: 30 computers + additional peripheral devices like printers.
 Network speed: Consider at least 1 Gbps for smooth operation.
 Internet access: Decide if the LAN will be connected to an external network.
 Security needs: Implement user authentication, firewall, and access control.
2. Network Topology Selection
A star topology is ideal, where all devices connect to a central switch.
3. Hardware Selection
 Router: A high-performance router for external connectivity.
 Network switch: A 48-port Gigabit Ethernet switch (to allow for future
expansion).
 Network cables: Cat6 Ethernet cables for fast and stable connections.
 Access points: If Wi-Fi is needed, install dual-band access points.
 Servers: Optional, for centralized control of files, applications, or authentication.
4. IP Addressing & Configuration
 Use DHCP (Dynamic Host Configuration Protocol) to assign IP addresses
dynamically.
 Create VLANs (Virtual LANs) if segregation between students and faculty is needed.
 Configure firewalls and antivirus for security.
5. Software & Security
 Install network monitoring tools for troubleshooting and performance analysis.
 Set up user authentication (Active Directory or similar).
 Configure access controls to prevent unauthorized usage.
6. Testing & Maintenance
 Perform speed tests to ensure efficient bandwidth distribution.
 Schedule regular updates and security checks.
✅ Network Design Overview
🌐 Topology: Star Topology
📋 Devices Required:
Device Quantity Description
Switch (48-port) 1 Central device to connect all clients
Router 1 For internet access and routing
Ethernet cables 30+ To connect each PC to the switch
PCs (clients) 30 Lab computers for students
Server (optional) 1 For file sharing, authentication, etc.
Wireless Access Point (optional) 1–2 For wireless access (for laptops, etc.)
Patch Panel (optional) 1 For cable management
UPS (optional) 1 For power backup
🔧 IP Addressing Scheme (Private Network)
 Network ID: [Link]/24
 IP Range: [Link] – [Link]
 Default Gateway: [Link] (Router)
 Static/DHCP: Use DHCP server on router or dedicated server

📊 Logical Diagram
1
Here is the network topology diagram:
[Internet]
|
[Router]
|
[Switch (48-port)]
--------------------------------------------------
| | | ... | |
PC1 PC2 PC3 ... PC30
 All PCs connect to the central switch
 The switch connects to the router for internet access
 The router may have firewall/NAT/DHCP functionality
 A server (optional) can be added to the switch for internal services
Setup Notes
 Use Cat6 Ethernet cables for better speed and futureproofing
 Assign static IP to the server and router
 Enable DHCP on router or server for client IP assignment
 Use a managed switch if you want VLANs or monitoring features
 Add access points if wireless access is required
 Network Diagram (Image)
 Here is a drawing of the topology and devices:
 Image created

Q2. Design a MAN for a city of 0.5 million people.

Ans: Designing a Metropolitan Area Network (MAN) for a city of 500,000 people requires
robust infrastructure, high-speed connectivity, and scalable solutions. Here’s how you could
approach it:
1. Network Objectives
 Coverage: City-wide with multiple access points.
 Speed & Bandwidth: Multi-gigabit fiber-optic backbone.
 Security: Encryption, firewalls, and user authentication.
 Scalability: Expandable for future growth.
2. Network Topology

2
  Hybrid Topology combining fiber-optic backbone with wireless access points.
 Ring Topology for redundancy: If one link fails, data reroutes automatically.
3. Core Infrastructure
 Fiber-optic backbone connecting key locations.
 Data centers for centralized management.
 High-capacity routers and switches for traffic control.
4. Connectivity & Access
 Wi-Fi Hotspots across public areas.
 Broadband service providers for homes and businesses.
 Cellular towers & 5G integration for mobile users.
5. IP Addressing & Management
 IPv6 deployment for large-scale IP addressing.
 Traffic optimization using SDN (Software-Defined Networking).
6. Security & Maintenance
 Network monitoring systems for fault detection.
 Cybersecurity measures (firewalls, intrusion detection).
 Redundant connections for reliability.
To design a Metropolitan Area Network (MAN) for a city of 0.5 million people, we must
consider scalability, high-speed connectivity, redundancy, and secure communication across
neighborhoods, institutions, and service centers.
✅ Network Design Overview
📍 Network Type: Metropolitan Area Network (MAN)
Coverage:
 Government buildings
 Educational institutions
 Hospitals
 ISPs/Data Centers
 Public Wi-Fi zones
🌐 Proposed Topology: Dual Ring Topology (with Star at Local Nodes)
🔁 Why Dual Ring?
 Redundant path in case of failure
 Fast recovery (supports SONET/SDH protocols)
 Scalable for urban layouts
📋 Devices and Infrastructure
Component Description
Core Routers High-performance routers connecting rings and data centers
Metro Ethernet Switches For high-speed access and aggregation
Fiber Optic Cables Backbone for high bandwidth and low latency
Access Routers At local nodes (e.g. schools, hospitals)
Firewalls Security at key nodes
Wireless Access Points For public areas (e.g. parks, libraries)
Data Centers Hosting cloud services and central applications
UPS + Generators For backup power at critical nodes
🔢 Design Principles
 Backbone: High-speed fiber rings using Metro Ethernet or SDH/SONET
 Local Distribution: Star topology with Ethernet/fiber
 Routing Protocols: OSPF, BGP (if multiple ISPs involved)
 Redundancy: Dual-homing, automatic failover
 Security: Firewalls, Intrusion Detection Systems (IDS)

3
 Network Diagram
The diagram below shows the Dual Ring MAN topology with connected districts and data
centers:

Q3. Design a WAN for an organization located in different parts of the country.
Ans: Designing a Wide Area Network (WAN) for a nationwide organization requires a
reliable, scalable, and secure infrastructure. Here’s how you can approach it:
1. Network Objectives
 Connectivity: Seamless communication between multiple branches.
 Speed & Bandwidth: High-speed links for smooth data exchange.
 Security: Encryption, VPNs, and access control.
 Scalability: Future expansion possibilities.
2. Network Topology
A Hybrid Topology combining different architectures based on location needs:
 Hub-and-Spoke Model: A central data center connects branch offices.
 Full Mesh Connectivity: Important locations get direct links for better speed.
3. Connectivity Options
 MPLS (Multiprotocol Label Switching): Ensures efficient data routing.
 Dedicated leased lines or fiber-optic connections for high-speed, low-latency
communication.
 SD-WAN (Software-Defined WAN): Optimizes traffic across multiple links.
 VPN (Virtual Private Network): Ensures secure remote access.
4. Core Infrastructure
 Data centers for centralized storage and applications.
 High-performance routers and switches for data distribution.
 Cloud integration for flexibility and remote access.
5. Security & Management
 Firewalls & Intrusion Detection Systems for cybersecurity.
 Network monitoring tools to track performance.

4
  Redundant backup systems for failover protection.
To design a Wide Area Network (WAN) for an organization with offices across different
parts of a country, we need a scalable, secure, and reliable architecture that supports data
communication across long distances. The most suitable and modern topology is Hybrid
WAN using MPLS/VPN/SD-WAN, but for basic understanding, a Mesh or Partial Mesh
Topology is often used.
✅ Network Design Overview
🌐 Network Type: Wide Area Network (WAN)
🧭 Scenario:
 Head Office (Central Hub)
 4 Regional Branches in different cities
 Remote Access for traveling employees
📊 Recommended Topology: Partial Mesh Topology
 Central hub connects to each branch
 Branches can also communicate with each other (for redundancy or data sync)
 VPN/SD-WAN or MPLS lines used for secure and fast communication
📋 Devices and Technologies
Component Description
Core Router At Head Office, handles routing to all branches
Branch Routers At each branch, connects to Head Office and possibly to
other branches
Modems / CSU/DSU Interface with leased lines or ISPs
Firewalls For security at all sites
VPN Gateways For secure connections over public internet
SD-WAN Controllers Smart routing and failover
(optional)
Leased Lines/MPLS High-speed, private lines between major branches
Wireless Routers/APs For LAN at each location
Network Management For centralized monitoring
Server

Technology Used
 MPLS or VPN tunnels between sites
 IP addressing: Unique subnets for each branch (e.g., [Link]/24, [Link]/24, etc.)
 Routing Protocols: BGP, OSPF (for dynamic routing)

Network Diagram
The image below shows the WAN layout with one head office and multiple regional branches
connected through routers, with cloud representation for the internet/MPLS backbone:
Image created

5
📊 Comparison Table of Popular Network Operating Systems (NOS)
NOS License Type Best For (LAN Key Features Use Cases
/ MAN / WAN)
Microsoft Paid LAN, WAN Active Directory, Enterprises, academic
Windows DNS, DHCP, labs, corporate networks
Server Group Policy, file
sharing, Hyper-V
Red Hat Paid LAN, MAN, Secure shell Data centers, enterprises
Enterprise WAN access, enterprise-
Linux grade networking,
(RHEL) SELinux,
clustering
Cisco IOS Paid (bundled MAN, WAN Routing, ISP backbones,
(Internetwork with Cisco switching, QoS, enterprise WANs
OS) routers/switches) VPN, firewall,
MPLS
Juniper Paid (bundled) MAN, WAN Advanced routing Telecom, data centers,
JUNOS (BGP, OSPF), backbone ISPs
firewall, SDN,
MPLS support
pfSense Free (Open LAN, WAN Firewall, VPN, SMBs, schools, remote
Source) routing, captive offices
portal, load
balancing
MikroTik Paid (low-cost LAN, MAN, Routing, firewall, ISPs, WISPs, educational
RouterOS license) WAN hotspot, bandwidth networks
shaping, wireless
AP support

6
 VyOS Free (Open MAN, WAN CLI-based routing, Data centers, telcos,
Source) VPN, firewall, advanced users
NAT
Ubuntu Free (Open LAN, WAN SMB/NFS file Labs, developers,
Server Source) sharing, SSH, lightweight servers
DHCP/DNS
servers, secure
updates
OpenWrt Free (Open LAN, small Embedded Linux Home routers, labs, IoT
Source) MAN for routers, gateways
supports custom
networking stacks
TrueNAS Free (Open LAN NAS/SAN, File servers in LANs,
Core Source) NFS/SMB, educational use
snapshots,
replication
Solaris Paid LAN, WAN ZFS file system, Legacy systems, large-
(Oracle) scalability, strong scale file servers
networking tools
ClearOS Freemium LAN, WAN Web-based admin Small business networks
GUI, firewall,
email, content
filter
Zentyal Freemium LAN Linux-based Small/medium business
Server alternative to networks
Windows Server
(AD, DHCP, DNS,
Samba)
📝 Notes:
 LAN NOS: Emphasis on file/printer sharing, user authentication, and access control.
 MAN/WAN NOS: Focus on routing, switching, high-speed data transport, and secure
remote communication.
 Freemium: Core functionality free, but advanced modules or support are paid.
 Many commercial NOS (e.g., Cisco IOS, Junos) are bundled with hardware.

Here is a tabular list of popular brands for each of the key network infrastructure
devices used in LAN, MAN, and WAN setups, especially in enterprise and ISP
environments:
📊 Popular Brands for Networking Devices
Device Type Popular Brands
Core Routers - Cisco (ASR, NCS series)
- Juniper (MX Series)
- Huawei (NetEngine series)
- Nokia (7750 SR)
Branch Routers - Cisco (ISR Series)
- Aruba (HP)
- Fortinet (FortiGate)
- MikroTik (CCR/Hex series)
Modems / CSU/DSU - Cisco

7
 - Netgear
- TP-Link
- Motorola
- Digi International
Firewalls - Palo Alto Networks
- Fortinet (FortiGate)
- Cisco (Firepower)
- Sophos
- Check Point
VPN Gateways - Cisco (Adaptive Security Appliance - ASA)

- Juniper (SRX Series)

- Fortinet (FortiGate)
- SonicWall
SD-WAN Controllers (optional) - Cisco Viptela
- VMware Velocloud
- Fortinet Secure SD-WAN
- Versa Networks
- Silver Peak (Aruba)
Leased Lines / MPLS - Provided by ISPs/Telcos such as:
- AT&T
- BT
- Reliance Jio
- Tata Communications
- NTT
Wireless Routers / APs - Ubiquiti (UniFi)
- Aruba (HP)
- Cisco Meraki
- TP-Link Omada
- Netgear ProSafe
Network Management Servers - SolarWinds
- Nagios
- ManageEngine OpManager
- PRTG Network Monitor
- Zabbix

📝 Notes:
 Enterprise-grade devices typically come from Cisco, Juniper, Fortinet, and HP.
 Consumer and SMB-grade devices often include TP-Link, Netgear, MikroTik, and
Ubiquiti.
 Network Management Servers help monitor, alert, and manage the entire
infrastructure from a central location.

Designing a Library Management System

Example: Library Management System
A library needs to manage its books, members, and transactions. Here’s how we would model
and design a database system for this:
1. Identifying Requirements
 The system should store details of books, members, and borrowing records.
 Each book should have an ID, title, author, publisher, and availability status.

8
  Members should have a unique ID, name, contact details, and membership type.
 Borrow records should include which member borrowed which book, the borrowing
date, and the due date.
2. Designing Tables
We use a relational database model and define tables:

Books Table
BookI Title Author Publisher Available
D
1 Database Systems C.J. Date Pearson Yes
2 Programming SQL John Doe O'Reilly No

Members Table
MemberID Name Contact Membership Type
101 Shreya 987654321 Premium
0
102 Amit 923456789 Regular
0

Borrow Records Table

BorrowID MemberID BookID BorrowDate DueDate
1 101 2 2025-05-01 2025-05-15
3. Implementing the Database
We use SQL to create and manage tables:

CREATE TABLE Books ( BookID INT PRIMARY KEY, Title VARCHAR(100), Author
VARCHAR(100), Publisher VARCHAR(100), Available BOOLEAN );

CREATE TABLE Members ( MemberID INT PRIMARY KEY, Name VARCHAR(100),

Contact VARCHAR(15), MembershipType VARCHAR(50) );

CREATE TABLE BorrowRecords ( BorrowID INT PRIMARY KEY, MemberID INT

REFERENCES Members(MemberID), BookID INT REFERENCES Books(BookID),
BorrowDate DATE, DueDate DATE );

4. Querying the Database

To get the list of available books:
SELECT * FROM Books WHERE Available = 'Yes';

To check which books a member has borrowed:

SELECT * FROM BorrowRecords WHERE MemberID = 101;

This is a simple yet functional database model that demonstrates designing, modeling, and
implementing a DBMS.
Here is a comprehensive list of popular paid and unpaid (open-source/free) DBMS
systems, along with brief descriptions in a tabular format:
📊 Comparison Table of Popular DBMS Systems
DBMS License Type Key Features Use Cases

9
 Type
Oracle Paid Relational Highly scalable, Enterprise apps,
Database (RDBMS) supports PL/SQL, finance, government
ACID-compliant,
RAC, analytics,
cloud-ready
Microsoft SQL Paid Relational T-SQL support, BI Business intelligence,
Server (RDBMS) tools, Always On, CRM, ERP
integration with
Microsoft stack
IBM Db2 Paid Relational High-performance Banking, data
(RDBMS) queries, strong warehousing, legacy
analytics support systems
SAP HANA Paid In-memory, High-speed Enterprise analytics,
columnar DB processing, real- SAP ERP systems
time analytics,
complex queries
Amazon Paid (Cloud) Relational Fully managed, Web applications,
Aurora (MySQL/PgSQL) scalable, high SaaS, cloud-native
availability apps
MongoDB Freemium NoSQL Schema-less, JSON- IoT, real-time apps,
Atlas (Cloud) (Document) like docs, auto- catalogs
sharding, horizontal
scaling
PostgreSQL Free (Open Relational Advanced SQL, General-purpose, GIS,
Source) (RDBMS) extensible (PostGIS, analytics
JSONB), strong
consistency
MySQL Free (Open Relational Widely used, Websites, CMS,
Source) (RDBMS) simple, replication, small-medium apps
InnoDB engine
MariaDB Free (Open Relational MySQL fork, Web services, LAMP
Source) (RDBMS) improved stack
performance and
security
SQLite Free (Public Relational Lightweight, Mobile apps,
Domain) (Embedded) serverless, portable browsers, embedded
devices
Firebase Freemium NoSQL Real-time sync, Mobile, gaming, chat
Realtime DB / (Cloud) (Document) mobile/web-first, apps
Firestore serverless
Cassandra Free NoSQL (Wide High availability, IoT, telecom, time-
(Apache Column) eventually series data
License) consistent, huge
scale
Redis Free (Open NoSQL (Key- In-memory, ultra- Caching, real-time
Source) Value Store) fast, supports analytics, pub-sub
caching and streams
Neo4j Freemium NoSQL (Graph Graph traversal, Fraud detection, social

10
 DBMS) Cypher query networks
language
CockroachDB Freemium Distributed SQL PostgreSQL Global apps,
(Cloud/OSS compatible, distributed systems
) horizontal
scalability, strong
consistency
📝 Notes:
 Relational DBMS (RDBMS): Use structured tables, SQL for queries, support ACID
properties.
 NoSQL DBMS: Designed for unstructured/semi-structured data (e.g., document, key-
value, graph, columnar).
 Freemium: Core is free; paid versions include cloud features, support, or advanced
tools.

Q - Design a distributed database for a large bank having branches all over the world and
headquartered in India.
Ans: Designing a Distributed Database for a Global Bank
A distributed database system for a bank with branches worldwide must ensure scalability,
security, consistency, and fault tolerance while supporting transactions across multiple
locations. Here’s a structured approach:
1. Key Considerations
 Data Distribution: Each branch needs access to customer records, transaction logs,
and regulatory compliance data.
 Consistency & Availability: Ensuring real-time updates without compromising
performance.
 Security & Compliance: Adhering to local banking regulations and encrypting
sensitive data.
 Fault Tolerance & Backup: Replication mechanisms to prevent data loss.
2. Database Architecture
a) Distributed Database Model
A Hybrid Distributed Database System combining:
 Central Database at Headquarters (India) for core banking functions.
 Regional Databases in key locations like the US, Europe, and Asia.
 Local Branch Servers for high-speed transactions with periodic synchronization.
b) Replication Strategy
Multi-Master Replication: Each regional database synchronizes changes with others to
ensure consistency.
c) Sharding Strategy
 Customer Data Sharding: Customers grouped based on geographic region.
 Transactional Data Sharding: Distributed based on frequency and volume.
3. Tables & Structure
Customer Table
CustomerID Name Address Country AccountTyp BranchID
e
101 Shreya Kolkata, India India Savings 1001
Account Table
AccountID CustomerID Balanc Currency CreatedDate
e
50001 101 10,000 INR 2025-01-01

11
Transaction Table
TxnID AccountI Amount TxnType TxnDate BranchID
D
9001 50001 1000 Credit 2025-05- 1001
29
Branch Table
BranchID Location Country Region DatabaseServer
1001 Kolkata India Asia DB-Asia-01
4. SQL Implementation
Creating Tables
CREATE TABLE Customers ( CustomerID INT PRIMARY KEY, Name VARCHAR(100),
Address VARCHAR(255), Country VARCHAR(50), AccountType VARCHAR(50),
BranchID INT );

CREATE TABLE Accounts ( AccountID INT PRIMARY KEY, CustomerID INT

REFERENCES Customers(CustomerID), Balance DECIMAL(12,2), Currency
VARCHAR(10), CreatedDate DATE );

CREATE TABLE Transactions ( TxnID INT PRIMARY KEY, AccountID INT

REFERENCES Accounts(AccountID), Amount DECIMAL(12,2), TxnType
VARCHAR(10), TxnDate DATE, BranchID INT );
5. Ensuring Security & Compliance
 Encryption: AES-256 for financial transactions.
 Access Control: Role-based permissions (e.g., Teller, Manager, Admin).
 Regulatory Compliance: Data localization policies per country.
6. Synchronization & Backup Strategy
 Eventual Consistency with periodic syncs.
 Automated Backups to distributed cloud storage.
 Failover Mechanism to reroute transactions during downtime.
This structure ensures high availability, security, and seamless transactions across global
branches.

Designing a Distributed Database Management System (DDBMS) for a large

multinational bank headquartered in India involves complex architecture that ensures
availability, scalability, consistency, and fault tolerance across all global branches.
✅ DDBMS Design Overview
🌍 Scenario:
 Headquarters in India (Main Data Center)
 Regional Data Centers in 5 continents
 Dozens of branch offices per region
 Real-time banking transactions
 High availability and disaster recovery
🧱 Architecture Type: Hybrid Distributed Database
A hybrid DDBMS uses a combination of Replication and Partitioning:
 Horizontal Partitioning: Each region stores data of its local customers.
 Replication: Critical data (e.g. core account balances, fraud logs) is replicated across
key regions.
 Global Directory/Metadata Server: Keeps track of where each data fragment is
located.
Database Components

12
 Component Description
Data Nodes (DB Servers) Store actual data (partitioned and/or replicated)
Transaction Manager (TM) Manages distributed transactions and coordinates commits
Query Processor (QP) Parses and optimizes user queries, forwards subqueries
Global Catalog/Directory Metadata management system; tracks where data is stored
Replication Controller Manages sync and versioning of replicated data
Load Balancer Balances read/write loads across nodes
Backup & Recovery System Regular snapshots, failover mechanisms
WAN Optimization Enhances data transfer efficiency across continents
🔧 Devices Used
Device/Software Function
Enterprise DBMS (e.g., Oracle, PostgreSQL, Core DDBMS software
MongoDB)
Database Servers Host databases at each region
Application Servers Host banking applications
Router/Switches Manage internal/external
communication
Firewall/VPN/IDS Ensure secure data exchange
Cloud/Hybrid Storage For off-site backup, archival storage
⚙️How DDBMS Works
1. Data Fragmentation
 Horizontal: Each continent handles its customers.
 Vertical: Transaction logs and audit trails handled separately.
2. Data Replication
 Account summaries and KYC data are replicated globally for access and fault
tolerance.
3. Distributed Query Processing
 User query → Parsed by Query Processor → Subqueries routed to local/remote data
nodes → Aggregated result.
4. Distributed Transaction Management
 2-Phase Commit Protocol (2PC) or Paxos/Raft for ensuring consistency across
sites.
5. Concurrency & Deadlock Control
 Distributed locking or timestamp ordering
 Isolation levels enforced by local TM + global coordinator
6. Failure Recovery
 Data centers use checkpoints, log-based recovery, failover replicas.
Security and Compliance
 End-to-end encryption (TLS)
 Role-based Access Control (RBAC)
 Compliance: GDPR, RBI norms, ISO 27001
Distributed Database Topology Diagram
Below is a visual showing the DDBMS topology for the global bank, highlighting
headquarters, regional data centers, replication links, and local branch access:

13
Here is a list of popular paid and unpaid Distributed Database Management Systems
(DDBMS), along with brief descriptions in a tabular format:
📊 Comparison Table of Popular DDBMS Systems
DDBMS License Type Key Features Use Cases
Oracle RAC Paid Real Application Clusters, Banking, ERP,
automatic failover, high Enterprise Apps
availability, ACID-
compliant
Microsoft SQL Paid High availability groups, Financial systems,
Server (Always replication, transactional enterprise apps
On) consistency
IBM Db2 Paid High-performance Mainframes,
distributed SQL, data financial services
warehousing
Google Spanner Paid (Cloud) Global-scale distribution, Cloud-native apps,
horizontal scaling, strong fintech, gaming
consistency, SQL support
Amazon Aurora Paid (Cloud) MySQL/PostgreSQL Web apps,
(Global) compatible, auto-scaling, analytics, SaaS
multi-region replication
MongoDB Atlas Freemium Document-oriented, auto- IoT, mobile,
(Cloud) sharding, multi-cloud global catalogs, content
clusters apps
Cassandra Free (Apache Decentralized architecture, IoT, social media,
License) highly available, eventual messaging
consistency platforms
CockroachDB Freemium Strong consistency, SaaS, fintech,
(Cloud & On- PostgreSQL-compatible, global apps
prem) distributed SQL
PostgreSQL + Freemium Distributed PostgreSQL Analytics,
Citus (Citus is open- with horizontal scaling dashboards, OLAP
source + paid workloads
extensions)
MariaDB Xpand Freemium MySQL-compatible, Cloud applications,
distributed SQL engine, e-commerce
strong consistency
TiDB Open-source Distributed SQL with HTAP Real-time analytics
support, MySQL-compatible + transactions

14
 (HTAP)
YugabyteDB Open-source Distributed SQL, Cloud-native,
PostgreSQL-compatible, microservices
global consistency
Neo4j AuraDB Paid (Cloud) Graph DDBMS, supports Fraud detection,
global scale, ACID- recommendation
compliant systems
FoundationDB Open-source Key-value + ACID Apple’s backend,
transactions, supports low-latency
layered models workloads

📝 Notes:
 Freemium: Core product is free; advanced features or hosting require payment.
 Paid (Cloud): Fully managed with SLA, usually priced per usage or subscription.
 Open-source: Free to use and deploy, community-supported.

15