24 Comments

Nice article!

I'm curious on the decision from our two engineers to handle the database on their own for many of the initial phases instead of offloading to a fully managed database service in AWS (DDB or RDS depending on needs).

What could be the reasons they decided to host them in EC2 instances? Costs? A particular DB technology not offered as a service in AWS?

Expand full comment
author

RDS should be enough in this context. I forgot to mention it.

Thanks, Fran.

Expand full comment

excellent article and well explained

Expand full comment
author

thanks

Expand full comment
Dec 6, 2023Liked by Neo Kim

Great , brilliant way of explaining.

Expand full comment
author

thanks for the feedback

Expand full comment

This was absolutely brilliant ❤️👏🏾

Expand full comment
author

thanks for the feedback, Kelvin

Expand full comment

Loved the story format! It keeps the article engaging :)

A question though - won't the pre-launch stack be enough for steps 1-3? I'm doing a small project myself, and we indeed chose Amplify, Lambda and RDS. What's the advantages of an EC2 instance versus Lambdas? Cost savings?

Expand full comment
author

Lambdas are billed based on the execution time. So if you have infrequent and short execution time, lambdas are a good fit.

But if you have long running and CPU intensive execution, EC2 might be cheaper. Again, it depends on the use case.

It would be interesting to know more about your side project. It's pretty cool that you've something.

Expand full comment

Thanks!

It’s the first time I’m playing with serverless, so there are interesting lessons. Up until now I only used k8s (on GCP), with microservices.

Hopefully I’ll reach the milestones you wrote about and I will gladly share my experience :)

Expand full comment
author

fingers crossed :)

Expand full comment

Amazing article! Inspires me to build something and scale it out haha!

Expand full comment
author

nice

Expand full comment

Well written. Thanks for penning it down.

Expand full comment
author

thanks

Expand full comment
Dec 10, 2023Liked by Neo Kim

This is awesome! So comprehensive and engaging.

I’m struggling a bit on Step 6 though specifically the Load balancer part and diagram. Any resources I can explore to understand that in detail?

Expand full comment
author

thanks, perhaps this will might be useful https://www.nginx.com/resources/glossary/load-balancing/

Expand full comment

Nice presentation and explanation. I would have loved to see the full layout of the architecture at the final stage. That would help put perspective to the final solution. Nonetheless, thanks for sharing.👏🏽👏🏽👏🏽

Expand full comment

A bit late to this one, very good article!

But you lost me at the NoSQL throwaway line at the end. Since the NoSql hype rocket has come back to earth there are many ways to store and query JSON data orher than something like Mongo DB.

Add some JSON columns to MySql/Postgres, or stick it on S3.

Expand full comment

Nice Article! Loved the story format!

I have a question about S3 and CloudFront mentioned in step 5. What could be the usecase to use both? Won't S3 be enough to host images, css and javascript?

Expand full comment

S3 would be good enough to host content, however to reduce latency especially for cross-geographical users CDN(Content delivery network) is mostly used. CloudFront is managed CDN offering from AWS.

In many use-cases, S3 and cloudFront are used together.

Expand full comment

Well put. Interesting to see what problems were faced at different levels, and decision taken to overcome them. Thanks, really great article!

Expand full comment

Great post, excellent story.

Expand full comment
Error