Should I implement RabbitMQ and a custom backend now or wait until necessary?

0
7
Asked By TechWhiz42 On

As a solo developer, I'm currently building a tutoring marketplace and I've got a few features done like authentication, bookings, messaging, and calendar sync. I haven't started on Stripe Connect for payments yet, and I'm pondering whether to add RabbitMQ for asynchronous job processing and a separate backend using NestJS on AWS EC2. I plan to keep Supabase for database and authentication, but I'm unsure if I should implement these changes now or wait until I actually need them. I want to get a full view of what I can tweak before user traffic increases. For reference, my tech stack is Next.js and Supabase running on Vercel, which is working well at the moment. What do seasoned developers recommend regarding early setups versus waiting until issues arise?

5 Answers

Answered By CodeCrafter88 On

I'd skip RabbitMQ and a custom backend for now. It's easy to over-engineer things at the start. Concentrate on making everything work smoothly and see if those tools become necessary later on.

Answered By DevNinja99 On

Honestly, I would wait until you actually need it. You're just starting out with no users, so adding RabbitMQ could create unnecessary complexity. Focus on getting user feedback, building out features, and launching payments first. Once you start seeing real traffic and scaling challenges, then you can consider adding more infrastructure like a custom backend or RabbitMQ.

Answered By SimpleDevStory On

You might want to keep things straightforward and work with what you have. EC2 can be a hassle to manage, and you likely won’t hit those scaling issues until you have a solid user base.

Answered By FutureDevGuru On

I totally agree, hold off on those additions for the moment. Your priorities should be getting user feedback and improving your marketplace features; that’s a much better use of your time right now.

Answered By ScalingSeeker On

You could look into doing some load testing with a tool like Locust to see how many concurrent users you can really handle. This might help you find any existing bottlenecks before they become real problems, so you won’t have to rewrite everything later.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.