If you’re still confused about how you can scale your web application, remember these 3 things:
- Fill the bucket
- Replicate
- Distribute
Fill the bucket means adding more resources (cpu, RAM, disk space) to your application. When your service’s performance stops improving with more resources, move on to
Replicate, which is basically creating a copy of your service and changing your architecture so that you can handle incoming state mutations from different sources.
Finally, distribute! This basically means splitting your monolith backend into smaller services and distributing your logic amongst them.
DO NOT SKIP steps. Even if you think you’re ready technically, you team and org as a whole might not be ready financially or operationally for the impact! Consider carefully your constraints when tackling scale problems. Remember, solve for the present and near future, not for problems you “think will come” in the far future
▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬
- Twitter: https://twitter.com/bassemdy
- GitHub: https://github.com/link-
- LinkedIn: https://www.linkedin.com/in/bassemdghaidy
- Facebook: https://www.facebook.com/BassemDy
- Blog: https://blog.bassemdy.com
▬▬▬▬▬▬ Support the channel 💜 ▬▬▬▬▬▬
Every little bit helps ✨
- Get access to perks: https://www.youtube.com/channel/UC6iKOXJ9PD-n8DcFPBjLD0w/join
- Join the journey on Patreon: https://www.patreon.com/glich_stream
- 1 time support: https://www.buymeacoffee.com/glich.stream
#glichstream #softwareengineering