How to architect a scalable event and ticketing platform with Supabase, Strapi and Memberstack for a small development team?
Hi everyone!
I'm planning an event platform project and would love your input on the overall architecture before I get too deep into development.
π‘ Concept
The platform will allow:
-
Organizers (Free & Premium tiers) to manage events
-
Users to RSVP for free events or buy tickets
-
Donation-based memberships for supporters
π§ Planned Stack
-
Supabase: backend DB for:
-
Organizer Groups
-
Events
-
RSVP Lists
-
Potentially test resources
-
-
Strapi (or another Headless CMS):
-
Manage landing pages
-
Pull structured content into frontend
-
-
Memberstack:
-
Authentication & member management
-
Different roles: free users, supporters (donors), free/premium organizers
-
βοΈ Features
-
Event browsing and RSVP system
-
Ticket purchase system (eventually)
-
Dynamic landing pages for events or groups
-
Member dashboard depending on role (user/organizer)
β My Main Question
Is this feasible for a small team or solo developer using no-code/low-code tools (with custom code where needed)? Or am I walking into a trap thatβll need 6 full-stack devs and a year of work? π
Any feedback, warnings, or examples from similar builds would be hugely appreciated!
Comments
0 comments
Please sign in to leave a comment.