Member Avatar for rixcy

I'm currently building a museum membership management system using .NET and a relational database. The project is inspired by solutions like MembershipAnywhere, which help museums manage digital memberships and improve the visitor experience.

The system is designed to handle member registration, digital membership cards, QR code check-ins, membership renewals, notifications, and integrations with CRM and ticketing platforms. One of my main goals is to ensure the application remains responsive and reliable as the number of members grows.

I'm trying to decide on the best architecture for long-term scalability. Would you recommend starting with a modular monolith and moving to microservices later, or designing a service-based architecture from the beginning?

I'd also appreciate recommendations on caching, database optimization, background job processing, and monitoring for a museum membership platform with a large member base.

If you've built similar museum, nonprofit, or membership management systems, I'd love to hear what worked well and what challenges you encountered.

Edited by rixcy
  • 4 Contributors
  • 3 Replies
  • 47 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by Dani

Recommended Answers

All 3 Replies

Member Avatar for rproffitt

Given today's machines with SSD and more, I didn't see any impact at over 1 million on the member's list.

LESSON: Build it. Get it working.
DON'T OPTIMIZE AS A GOAL.

Get it working. Then see if something needs improvement.

Member Avatar for Salem

Where is your security in all that buzzword bingo?

Some naive attempt at implementation where you manage to store credit cards and passwords in clear text is well within your future, and a field day for any pedestrian hacker.

commented: "So the combination is... one, two, three, four, five? That's the stupidest combination I've ever heard in my life!" +16
Member Avatar for Dani

I don't have .net experience, but, based on creating DaniWeb, I can tell you to focus on creating a bare bones proof of concept, and then building out from there, being as agile as possible along the way. For caching, I would look into redis. For database optimization, I can only help with MySQL, which I assume isn't what you'll be using for your .net app.

commented: It's been over a decade but my .NET app did use MySQL and I thought it was the cat's pajamas! +16
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.