As is obvious from the title, we will talk about hosting and choosing a cloud server for placement: when it is better to set everything up yourself, and when to go to AWS and Google Cloud.
Introduction
First, a little educational program, and then we'll go into the stories of failure. It is extremely popular among our Western clients to immediately specify "development for AWS" in the requirements.
AWS provides a huge number of services for all occasions: databases, storage, various methods of computing. If you describe it very roughly, you host your mobile app development service project on AWS and don’t worry about the loads at all. Most often, this is Lambda , some kind of DB , plus file storage . Everything is automatically scaled: you don’t need to worry about what to do at peak load, you can easily forget that you need to increase the disk if the space runs out under the influx of downloaded content. Sounds simply fantastic! Google Cloud works in approximately the same way.
On the other hand, there are cloud server providers where you get a bare server, infrastructure, and sit and do everything yourself. We use DigitalOcean (yes, the link is an affiliate link, but we are not partners, we just want to earn $25 for a recommendation ).
Myths and reality
So let's develop the myths about the ease and accessibility of the first option, and the inaccessibility of the second.
In fact, your application will not be able to scale absolutely automatically with increasing loads without preliminary good preparation of the code. Yes, for example, your load has increased, + 100 servers will be added to execute the code, + 100 for the DB, but most often the bottleneck in all projects is the DB. You still will not be able to speed up calculations on the DB side, and the application will die sooner or later if you have not done the proper preparation on the code side.
A big disadvantage of hosting on AWS is that the code is specifically created for integration with AWS. That is, you do not write, for example, that you need to connect to a database, but instead you write that you need to connect specifically to a database on AWS. Thus, you have already doomed your project to hosting exclusively on AWS.
