Hi everyone,
I’m currently building a digital card system for museums using Go programming (Golang), and I’d love to get some feedback from the GolangBridge community.
Museum members can keep their digital membership card in Apple Wallet or Google Wallet and use a QR code for quick entry instead of carrying a physical card. While the concept is straightforward, building a backend that can handle real-world traffic efficiently is the real challenge.
One thing I’m trying to optimize is QR code validation during busy hours when many visitors arrive at the same time. Since Go is known for its concurrency and performance, it feels like a good choice, but I’m interested in learning how experienced Go developers would design a system like this.
Would you build it as a modular monolith first or start with microservices? How would you handle caching, database queries, and concurrent requests without making the architecture unnecessarily complex?
If you’ve built similar high-traffic applications with Go programming (Golang) or have lessons learned from production systems, I’d really appreciate hearing your approach. Real-world experience is always more valuable than theoretical examples.