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
Great article! Simplistically shares insight into the scaling journey available with GCP. Curious, (and if I can’t find it, sorry) - do you have a comparison of GCP vs. AWS/other cloud options?
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 😉
GCP is one of those providers I always wanted to explore deeply.
Thanks for sharing this introduction, Neo!
you're welcome
Thanks! Do you have any similar advice for Azure?
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
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
true, you're right.
Great article! Simplistically shares insight into the scaling journey available with GCP. Curious, (and if I can’t find it, sorry) - do you have a comparison of GCP vs. AWS/other cloud options?
Nice article, as you said in article it is not specific to any cloud service. It is a generalized content which can be used in all cloud services.
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 😉
👏
Sweet. Thank you!
Simply and straightforward explanation on how to scale an application! Thanks for that Neo!
I appreciate the content and the approach used to deliver it here. Thank you for sharing.
Solid breakdown my friend, with much leanings in it! Keep rocking it!
thanks, Daniel
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.