In this article, we’ll go through a low-level design (LLD) implementation of a parking lot system in Go. We'll explore different aspects of the system and see how each component interacts with the rest. This implementation focuses on clarity and real-world usefulness, so you can extend it easily if you want to add features like more vehicle types, multiple payment options, or spot reservations.
The system handles tasks like managing parking floors and spots, parking and unparking vehicles, and processing payments. We’ll also ensure it’s thread-safe for concurrent access, so if we need to expand it into a larger system, it won’t break down under pressure.
Core Components
Our design includes six main components:
- Parking Lot - The main entry point managing floors and parking operations.
- Parking Floor - Each floor contains multiple parking spots for different types of vehicles.
- Parking Spot - Represents a parking spot that can hold a specific type of vehicle.
- Parking Ticket - Tracks entry/exit times, parking charges, and the associated vehicle.
- Payment System - Handles parking fee calculations and payment processing.
- Vehicle Types - Supports different types of vehicles (cars, vans, trucks, and motorcycles). Each type has a different hourly charge.
Singleton Parking Lot
Our ParkingLot uses the Singleton pattern. This means there’s only one instance of the parking lot, which is created once and reused across the application. Here’s the code to get that working:
var ( parkingLotInstance *ParkingLot once sync.Once ) type ParkingLot struct { Name string floors []*ParkingFloor } func GetParkingLotInstance() *ParkingLot { once.Do(func() { parkingLotInstance = &ParkingLot{} }) return parkingLotInstance }
Using sync.Once, we ensure that only one instance is created, even when accessed by multiple goroutines.
Managing Floors in the Parking Lot
The parking lot has multiple floors, each with designated parking spots for different vehicle types (e.g., cars, vans, trucks, and motorcycles). To add a floor to the parking lot, we use the AddFloor method:
func (p *ParkingLot) AddFloor(floorID int) { p.floors = append(p.floors, NewParkingFloor(floorID)) }
Each floor is created using the NewParkingFloor function, which organizes spots by vehicle type.
Parking Spots
Each ParkingSpot is associated with a specific vehicle type (like a car or motorcycle). This allows the system to manage and restrict which vehicles can park in each spot. Here’s the ParkingSpot structure and the ParkVehicle method:
type ParkingSpot struct { SpotID int VehicleType vehicles.VehicleType CurrentVehicle *vehicles.VehicleInterface lock sync.Mutex } func (p *ParkingSpot) ParkVehicle(vehicle vehicles.VehicleInterface) error { p.lock.Lock() defer p.lock.Unlock() if vehicle.GetVehicleType() != p.VehicleType { return fmt.Errorf("vehicle type mismatch: expected %s, got %s", p.VehicleType, vehicle.GetVehicleType()) } if p.CurrentVehicle != nil { return fmt.Errorf("parking spot already occupied") } p.CurrentVehicle = &vehicle return nil }
We use a Mutex lock to make sure only one vehicle can park in a spot at a time.
Parking Ticket
Every vehicle gets a ticket with the entry time, exit time, parking spot, and total charge. This ticket will be updated when the vehicle exits, and charges will be calculated based on the time spent parked.
var ( parkingLotInstance *ParkingLot once sync.Once ) type ParkingLot struct { Name string floors []*ParkingFloor } func GetParkingLotInstance() *ParkingLot { once.Do(func() { parkingLotInstance = &ParkingLot{} }) return parkingLotInstance }
The CalculateTotalCharge method calculates parking fees based on the vehicle type and duration.
Payment System
The PaymentSystem class processes the payment, updating the payment status based on whether the required amount is paid:
func (p *ParkingLot) AddFloor(floorID int) { p.floors = append(p.floors, NewParkingFloor(floorID)) }
The ProcessPayment function checks the amount and updates the payment status to Completed or Failed.
Adding Vehicle Types
Our system supports different types of vehicles (cars, vans, trucks, and motorcycles). Each type has a different hourly charge. This is achieved by setting up a VehicleType and VehicleInterface in a separate vehicles package:
type ParkingSpot struct { SpotID int VehicleType vehicles.VehicleType CurrentVehicle *vehicles.VehicleInterface lock sync.Mutex } func (p *ParkingSpot) ParkVehicle(vehicle vehicles.VehicleInterface) error { p.lock.Lock() defer p.lock.Unlock() if vehicle.GetVehicleType() != p.VehicleType { return fmt.Errorf("vehicle type mismatch: expected %s, got %s", p.VehicleType, vehicle.GetVehicleType()) } if p.CurrentVehicle != nil { return fmt.Errorf("parking spot already occupied") } p.CurrentVehicle = &vehicle return nil }
We can create new vehicles by calling NewCar, NewVan, NewTruck, etc., each of which implements VehicleInterface.
Bringing It All Together
Let’s see how the pieces fit together in a flow:
- Create a Parking Lot: Call GetParkingLotInstance() and add floors with AddFloor.
- Find Parking Spot and Park Vehicle: ParkVehicle method finds an available spot, validates it against the vehicle type, and generates a ticket.
- Unpark Vehicle and Process Payment: UnparkVehicle generates the total charge, initiates the payment system, and completes the transaction.
This parking lot system is a simplified starting point for building more complex systems. We covered the basics of floor and spot management, vehicle parking and unparking, and a basic payment process.
For full code implementation, check the following repository:
thesaltree
/
low-level-design-golang
Low level system design solutions in Golang
Low-Level System Design in Go
Welcome to the Low-Level System Design in Go repository! This repository contains various low-level system design problems and their solutions implemented in Go. The primary aim is to demonstrate the design and architecture of systems through practical examples.
Table of Contents
- Overview
- Parking Lot System
- Elevator System
- Library Management System
- Vending Machine System
- Social Media Platform
Overview
Low-level system design involves understanding the core concepts of system architecture and designing scalable, maintainable, and efficient systems. This repository will try to cover solutions of various problems and scenarios using Go.
Parking Lot System
The first project in this repository is a Parking Lot System. This system simulates a parking lot where vehicles can be parked and unparked. It demonstrates:
- Singleton design pattern for managing the parking lot instance.
- Handling different types of vehicles (e.g., cars, trucks).
- Parking space management across multiple floors.
- Payment processing for…
The above is the detailed content of System Design: Building a Parking Lot System in Go. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Golang is mainly used for back-end development, but it can also play an indirect role in the front-end field. Its design goals focus on high-performance, concurrent processing and system-level programming, and are suitable for building back-end applications such as API servers, microservices, distributed systems, database operations and CLI tools. Although Golang is not the mainstream language for web front-end, it can be compiled into JavaScript through GopherJS, run on WebAssembly through TinyGo, or generate HTML pages with a template engine to participate in front-end development. However, modern front-end development still needs to rely on JavaScript/TypeScript and its ecosystem. Therefore, Golang is more suitable for the technology stack selection with high-performance backend as the core.

To build a GraphQLAPI in Go, it is recommended to use the gqlgen library to improve development efficiency. 1. First select the appropriate library, such as gqlgen, which supports automatic code generation based on schema; 2. Then define GraphQLschema, describe the API structure and query portal, such as defining Post types and query methods; 3. Then initialize the project and generate basic code to implement business logic in resolver; 4. Finally, connect GraphQLhandler to HTTPserver and test the API through the built-in Playground. Notes include field naming specifications, error handling, performance optimization and security settings to ensure project maintenance

The key to installing Go is to select the correct version, configure environment variables, and verify the installation. 1. Go to the official website to download the installation package of the corresponding system. Windows uses .msi files, macOS uses .pkg files, Linux uses .tar.gz files and unzip them to /usr/local directory; 2. Configure environment variables, edit ~/.bashrc or ~/.zshrc in Linux/macOS to add PATH and GOPATH, and Windows set PATH to Go in the system properties; 3. Use the government command to verify the installation, and run the test program hello.go to confirm that the compilation and execution are normal. PATH settings and loops throughout the process

sync.WaitGroup is used to wait for a group of goroutines to complete the task. Its core is to work together through three methods: Add, Done, and Wait. 1.Add(n) Set the number of goroutines to wait; 2.Done() is called at the end of each goroutine, and the count is reduced by one; 3.Wait() blocks the main coroutine until all tasks are completed. When using it, please note: Add should be called outside the goroutine, avoid duplicate Wait, and be sure to ensure that Don is called. It is recommended to use it with defer. It is common in concurrent crawling of web pages, batch data processing and other scenarios, and can effectively control the concurrency process.

Using Go's embed package can easily embed static resources into binary, suitable for web services to package HTML, CSS, pictures and other files. 1. Declare the embedded resource to add //go:embed comment before the variable, such as embedding a single file hello.txt; 2. It can be embedded in the entire directory such as static/*, and realize multi-file packaging through embed.FS; 3. It is recommended to switch the disk loading mode through buildtag or environment variables to improve efficiency; 4. Pay attention to path accuracy, file size limitations and read-only characteristics of embedded resources. Rational use of embed can simplify deployment and optimize project structure.

The core of audio and video processing lies in understanding the basic process and optimization methods. 1. The basic process includes acquisition, encoding, transmission, decoding and playback, and each link has technical difficulties; 2. Common problems such as audio and video aberration, lag delay, sound noise, blurred picture, etc. can be solved through synchronous adjustment, coding optimization, noise reduction module, parameter adjustment, etc.; 3. It is recommended to use FFmpeg, OpenCV, WebRTC, GStreamer and other tools to achieve functions; 4. In terms of performance management, we should pay attention to hardware acceleration, reasonable setting of resolution frame rates, control concurrency and memory leakage problems. Mastering these key points will help improve development efficiency and user experience.

It is not difficult to build a web server written in Go. The core lies in using the net/http package to implement basic services. 1. Use net/http to start the simplest server: register processing functions and listen to ports through a few lines of code; 2. Routing management: Use ServeMux to organize multiple interface paths for easy structured management; 3. Common practices: group routing by functional modules, and use third-party libraries to support complex matching; 4. Static file service: provide HTML, CSS and JS files through http.FileServer; 5. Performance and security: enable HTTPS, limit the size of the request body, and set timeout to improve security and performance. After mastering these key points, it will be easier to expand functionality.

The purpose of select plus default is to allow select to perform default behavior when no other branches are ready to avoid program blocking. 1. When receiving data from the channel without blocking, if the channel is empty, it will directly enter the default branch; 2. In combination with time. After or ticker, try to send data regularly. If the channel is full, it will not block and skip; 3. Prevent deadlocks, avoid program stuck when uncertain whether the channel is closed; when using it, please note that the default branch will be executed immediately and cannot be abused, and default and case are mutually exclusive and will not be executed at the same time.
