14 Comments

GCP is one of those providers I always wanted to explore deeply.

Thanks for sharing this introduction, Neo!

Expand full comment

you're welcome

Expand full comment

Thanks! Do you have any similar advice for Azure?

Expand full comment

hey Henry, this is a generic approach, you can reuse these ideas across other cloud providers.

Don't forget: there are many ways to scale an app and this is just 1 of them. Thank you

Expand full comment

There is almost nothing specific to GCP in this article. Same concepts apply pretty much everywhere, outside or cloud too. Geo load balancing, CDN, cache, databases

Expand full comment

true, you're right.

Expand full comment

Funny story, I would consider some cloud native styles from the scratch instead starting from a virtual server: simply put your static web content on an object store, avoid to complex data structures from the beginning before having your hypothesis approved. If persistency is needed you might start from a json store like firebase ( it has some more opportunities in the cage if you start growing), put backend logic in a serverless runtime such as cloudRun (knative) or Cloudfunction and represent your environment in manifest, your copilot might help you to grow in with gcloud and terraform πŸ˜‰

Expand full comment

πŸ‘

Expand full comment

Sweet. Thank you!

Expand full comment

Simply and straightforward explanation on how to scale an application! Thanks for that Neo!

Expand full comment

I appreciate the content and the approach used to deliver it here. Thank you for sharing.

Expand full comment

Solid breakdown my friend, with much leanings in it! Keep rocking it!

Expand full comment

thanks, Daniel

Expand full comment
Comment deleted
Aug 20Edited
Comment deleted
Expand full comment

thank you for the feedback, Aman.

I need to improve my writing skills (still working on it). I'll keep this in mind for future articles.

Expand full comment