How thesaltree/low-level-design-golang works
Project type and purpose
• This is a monorepo of seven self-contained low-level system design examples in Go:
• ATM Machine
• Parking Lot
• Elevator System
• Library Management System
• Vending Machine
• Social Media Platform
• Meeting Scheduler
• Each subfolder implements a classic LLD problem showcasing specific design patterns, concurrency controls, and domain models.
File structure
• Top-level directories correspond one-to-one with the seven systems.
• A main.go entry point
• One or more domain/model files describing core entities (e.g., account, card, floor, elevator, book, member, product, user, room).
• Manager or state files encapsulating business logic (e.g., ATM states, parking lot singleton, elevator manager, post manager, meeting scheduler).
• The presence of files named “state.go”, “manager.go”, or “singleton” hints at specific patterns (State, Singleton, Facade, Observer, Chain of Responsibility).
README for additional insights
• The README outlines each system’s purpose, features, and key patterns:
• ATM: State, Chain of Responsibility, Template
• Parking Lot: Singleton, Payment Processing
• Elevator: Multi-elevator coordination, concurrency
• Library: Singleton, concurrency control, borrowing history
• Vending Machine: State Pattern, inventory & transaction handling
• Social Media: Facade, concurrency with RWMutex
• Meeting Scheduler: Observer pattern, calendar management