Eric Sun
Dec 8, 2020

https://techcrunch.com/2020/12/07/3-questions-to-ask-before-adopting-microservice-architecture

> The lack of a coherent definition for a service can cause teams to generate unnecessary overhead by creating too many similar services or spreading related services across different groups.

> Defining too many services creates unnecessary organizational and technical silos while increasing complexity and overhead.

> Their service definitions were too narrow, and by the time decomposition was complete, they were left with 4,000+ microservices to manage.

Just saw this today.

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

Eric Sun
Eric Sun

Written by Eric Sun

Advocate best practice of big data technologies. Challenge the conventional wisdom. Peel off the flashy promise in architecture and scalability.

No responses yet

Write a response