Community Information
-
Startup Infrastructure
First let's establish the tech stack: * Frontend: React * Backend: Node / Express / Supabase ( auth + db ) * Domain: Registered in Cloudflare Second why this post: While I know I could just throwing my projects into AWS without much consideration I would prefer to take an approach that meets these three criteria: **Simple:** While I could spend the next 1-4 weeks diving into how dev ops should be done and how to securely deploy my services in a way that won't bankrupt me if I make a mistake i'd prefer to focus on developing the product knowing that I can sleep at night without incurring a $5000 AWS bill for compute resources. Also simple in the sense that I wouldn't need to use too much of my time maintaining containers or updating things to keep it running. **Safe:** I'd like to know that I haven't misconfigured something in AWS in such a way that I can potentially cause some security vulnerability or allow bad actors to take our services down. **Scalable:** I'd also like that to an extent I could easily scale the frontend / backend to meet the needs of the business up until the point it is required to either hire or contract someone who actually knows how to build out these systems to be cost effective / scalable. Ideally it would be automated. Now to the point: I humbly accept that while with my current knowledge I could absolutely throw the projects into services in AWS and have them running just by hacking away at. While looking online on forums like Reddit I was looking at the managed services offered by AWS ( Amplify, Lightsail, Fargate, Cloudfront ect) and it seemed like a good fit where you can essentially pay slightly more but have AWS spin up all the services under the hood which complies with some kind of proven blueprint whereby you can focus more on the actual product and worry less about the infra. I seem to see a lot of contradicting posts on Reddit about these services suggesting to stay away and just simply "throw it in an ec2 instance" due to scalability or cost related issues. While I would love to dive into devops and really learn the ins and outs I've ended up in a tailspin of analysis paralysis in choosing the right solution to deploy version 1 to our customers and honestly on top of a 9-5 it's a bit much to not only then continue to develop / maintain the project but also to really understand / deep dive into devops. Would extremely appreciate suggestions / resources that would help me make some decisions deploying these services given the above criteria.3
© 2025 Indiareply.com. All rights reserved.