Hey everyone! I'm currently working on a college project where I'm building a service-based website. I initially only knew how to work with React and JavaScript for the frontend, so that's what I focused on. However, when it came time to develop the backend, I chose Node, Express, and MongoDB without fully considering my skills. Eventually, I created a backend using Supabase, but I just found out that I need to showcase Node, Express, and MongoDB in my project since that's what I originally proposed. Now, my plan is to use Supabase as my primary backend while incorporating Node, Express, and MongoDB for some microservices like adding to cart, confirming orders, and processing payments. Will this approach work? Any practical advice or alternative suggestions?
4 Answers
I'm not sure why you specifically need MongoDB. If it's just for showing your teachers, maybe you could simplify things by going straight to PostgreSQL instead of dealing with multiple databases. It might save you some headaches in the long run!
If you're already comfortable with React for the frontend, picking up Node shouldn't be too hard since it's also JavaScript. You might want to give it a shot! But I get that with deadlines looming, learning a whole new stack can be stressful.
Yeah, I get where you're coming from. The basics are manageable, but with the deadline so close, it can feel overwhelming.
Honestly, just stick with PostgreSQL for the project. It's much cleaner and easier to manage than juggling multiple systems.
Your plan might work, but I'd suggest you consider migrating Supabase to PostgreSQL since that's what it uses under the hood anyway. It'd save you the trouble of juggling four different databases, plus the teachers probably won’t notice the switch. You could just keep it simple!
Wow, I didn’t realize Supabase could easily be migrated to PostgreSQL! But what happens to Mongo? I’m worried my teachers will ask to see the backend code, which is why I thought I’d showcase Node and Express for those microservices.
Exactly, if they're picky about backend code, having everything clearly tied to one database would be less risky.
That’s a good point! I initially picked Mongo because it was part of my original plan. I figured I could include microservices just to make it look like I used it, but I want to keep it simple!