Member-only story
The architectural shift from monoliths to microservices came with a wide range of benefits. A reduction in complexity means the services are easier to design and build, the isolation of tasks means services can be team-specific, reducing the onboarding time for new developers and a reduction in processing power required to run the services makes it easier to scale horizontally.
But microservices come with one specific downside, you force front-end application developers to adopt the complexity that comes with consuming data from multiple sources, formatting the data and then, they can finally do their job and display the data. This goes against a fundamental rule for developing great APIs: absorb the complexity. When an API absorbs the complexity, the front-end developer is left to do what they do best, create user experiences that delight your customers.
So, a solution to this problem would:
- Allow backend developer to develop services that perform specific tasks and perform them well
- Allow site reliability engineers to scale services and maintain a reliable service for your customers
- Allow new developers to jump straight into a microservice and start delivering value
- Most importantly, allow front end developers to focus on building…
