Things to remember while building Microservices



856 views Designing μ-services



Microservices are much more than an engineering problem to solve and let’s look at some key engineering and non-engineering things to remember while building them.

Growth Opportunity

Microservices are a great growth opportunity given there are so many engineering and non-engineering challenges to solve. Every engineer or early leader should grab this opportunity to showcase his/her prowess and earn leadership brownie points.

Conflicts are inevitable

Engineers are passionate, and intra-team and inter-team conflicts are inevitable. But the conflicts should be gracefully by

  • taking data-driven informed decisions
  • consulting senior engineers
  • sometimes moving on without creating a fuss

Architecture Evolves

Vision evolves and so would our architecture. The decisions we took while building it might not be the best today and hence we should be okay with the code getting scrapped and seeing some dramatic changes in the flow.

Technical Debt

We cannot always build a Microservice in the best way possible. Engineering teams are always running against time and aim at delivering things quicker.

This requires us to cut some corners and make some inefficient decisions and this is called Technical Debt. Over time such debt piles up and reduces the development velocity.

It is important to clean up technical debt periodically, by reserving ~10% of the bandwidth of every engineer every sprint.

Enforcing Standardizations

Standardizations are essential for microservices as it provides a clear set of guidelines to use for building them.

To ensure that every team is not building and setting up their conventions from scratch, we create a Template that everyone can use and build on top of it. This aligns with the DRY principle ensuring we do not waste time doing repeated things.

Some engineers and teams might see standardization as strangling, and hence we might see a potential backlash. In order to ensure this is adopted smoothly

  • we should have a forum that decides the standards instead of a central team
  • the forum should have proper reasoning behind every decision taken for the template

This would help us keep such templates and best practices inclusive while ensuring a positive sentiment all around.

Business over Engineering

This is offensive, but it is true. Engineering exists because the business does and hence while building microservices we should always remain aligned with the strategic goals.

For example, if the business priority is profitability we should not have over-provisioned microservices that leak money.


Arpit Bhayani

Arpit's Newsletter

CS newsletter for the curious engineers

❤️ by 17000+ readers

If you like what you read subscribe you can always subscribe to my newsletter and get the post delivered straight to your inbox. I write essays on various engineering topics and share it through my weekly newsletter.




Other essays that you might like


BFF - Backend for Frontend - Pattern in Microservices

2225 views 114 likes 2022-07-04

As your application evolves, supporting multiple types of clients like Desktop, Mobile apps, etc becomes tricky. The bac...

Best practices that make microservices integration easy

850 views 50 likes 2022-06-27

Running microservices in isolation does not make any sense. To get something done, multiple microservices need to talk t...

Things to remember while building Microservices

856 views 35 likes 2022-06-20

An engineer working on Microservices should not only just focus on engineering; there are so many other aspects to look ...

Why should we have a standard way of building Microservices?

631 views 27 likes 2022-06-17

We all love creating microservices, but what if every team creates its own microservice uniquely and uses its own conven...


Be a better engineer

A set of courses designed to make you a better engineer and excel at your career; no-fluff, pure engineering.


System Design Masterclass

A masterclass that helps you become great at designing scalable, fault-tolerant, and highly available systems.

Enrolled by 700+ learners

Details →

Designing Microservices

A free course to help you understand Microservices and their high-level patterns in depth.

Enrolled by 17+ learners

Details →

GitHub Outage Dissections

A free course to help you learn core engineering from outages that happened at GitHub.

Enrolled by 67+ learners

Details →

Hash Table Internals

A free course to help you learn core engineering from outages that happened at GitHub.

Enrolled by 25+ learners

Details →

BitTorrent Internals

A free course to help you understand the algorithms and strategies that power P2P networks and BitTorrent.

Enrolled by 42+ learners

Details →

Topics I talk about

Being a passionate engineer, I love to talk about a wide range of topics, but these are my personal favourites.




Arpit's Newsletter read by 17000+ engineers

🔥 Thrice a week, in your inbox, an essay about system design, distributed systems, microservices, programming languages internals, or a deep dive on some super-clever algorithm, or just a few tips on building highly scalable distributed systems.



  • v12.4.4
  • © Arpit Bhayani, 2022

Powered by this tech stack.