Putting a product to production for the first time using AWS backend - its like a platform to look at ecommerce data which scrapes info from different websites for competitive analysis.
Ask HN: What should I be on the lookout putting my MVP to production using AWS?
1–7 of 7 posts
Re: Ask HN: What should I be on the lookout putting my MVP to production using AWS?
#2Costs, blindly following their reference architectures will get you lambdas everywhere and microsservices everywhere and other upsells that will cost you a lot. Also, do not use their WAF/CDN, again, costs.
Re: Ask HN: What should I be on the lookout putting my MVP to production using AWS?
#3Keep it as simple as possible.
Lambdas and all the serverless stuff is great until it isn't anymore, because you need another service for this and another service for that which gets a) complex quickly and b) expensive, too.
For an MVP, go EC2 or ECS and a database, possibly S3 storage depending on what you need. MVPs are all about learning about the problem in the most cost-efficient way possible
Re: Ask HN: What should I be on the lookout putting my MVP to production using AWS?
#4"AWS backend" can mean sooo many things - you will get better answers if you describe your architecture in a little more detail.
Re: Ask HN: What should I be on the lookout putting my MVP to production using AWS?
#5Keep it as simple as possible. Lambdas and all the serverless stuff is great until it isn't anymore, because you need another service for this and another service for that which gets a) complex quickly and b) expensive, too. For an MVP, go EC2 or ECS and a database, possibly S3 storage depending on what you need. MVPs are all about learning about the problem in the most cost-efficient way possible
For an MVP I'd consider installing the database itself on the EC2 instance backed by EBS volume as opposed to going with RDS. Ive done it and I was surprised how well it performed for zero additional cost. Take care NOT to install anything on the SSD attached to the EC2 instance as it gets wiped on instance reboot (and thats not always up to you). Additionally, use IP whitelisting/security groups to restrict access to YOUR public IP for things like said database etc. Regarding public IP addresses, spring the fractional dollar and get yourself an elastic IP. I know the EC2 instance will have a public IP associated it but that can change where the elastic one is relatively permanent.
Re: Ask HN: What should I be on the lookout putting my MVP to production using AWS?
#6"AWS backend" can mean sooo many things - you will get better answers if you describe your architecture in a little more detail.
EC2, SQS, S3, API Gateway, Cognito
Re: Ask HN: What should I be on the lookout putting my MVP to production using AWS?
#7Keep it as simple as possible. Lambdas and all the serverless stuff is great until it isn't anymore, because you need another service for this and another service for that which gets a) complex quickly and b) expensive, too. For an MVP, go EC2 or ECS and a database, possibly S3 storage depending on what you need. MVPs are all about learning about the problem in the most cost-efficient way possible
For an MVP I'd consider installing the database itself on the EC2 instance backed by EBS volume as opposed to going with RDS. Ive done it and I was surprised how well it performed for zero additional cost. Take care NOT to install anything on the SSD attached to the EC2 instance as it gets wiped on instance reboot (and thats not always up to you). Additionally, use IP whitelisting/security groups to restrict access t…
For an MVP a SQLite database will probably be good enough, too. You make some good points!
Alternatively, go rent a virtual server for a couple bucks a months somewhere