Chapter 86. Focus on Your Team, Not on the Cost
Guillaume Blaquiere
Public clouds come with a new capability: the real knowledge of cost. In my company, this generated fears: “Whoa, it’s expensive!” No, it isn’t—but the cost is known, visible. In an on-premises environment, it’s very hard to know the real cost per service, especially the human cost or the cost of mutualized resources (network, storage, hosting, etc.).
When you choose a technical solution, it’s important to take into account all the pieces of the project—and first of all, your human resources. Google Cloud Functions, AWS Lambda, or other FaaS solutions may seem cheaper because your use case fits them well. But is your team able to develop functions in the available languages and within the existing limitations?
The scalability and simplicity of these serverless solutions makes them popular, and companies have built entire new stacks on top of them. Some projects have thousands of functions, and it’s hard for a newcomer to understand the impact and the role of each one.
For a lot of teams that move to the cloud, splitting their monolith applications into microservices is a real challenge in terms of design, documentation, and organization. If you consider a simple microservice with four HTTP verbs (GET, POST, PUT, DELETE), FaaS architecture splits it into four parts. Functions ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access