10 Challenges in Adopting and Implementing Microservices

10 Challenges in Adopting and Implementing Microservices

We always hear great things about Microservices. But today let's talk about the top 10 challenges that come with adopting Microservices.

Managing Microservices

As the number of microservices increases, managing them becomes tough. If there is no plan or accountability then we might end up with a lot of tiny microservices or with a huge macro-service.

Extensive Monitoring and Logging

Monitoring what happens across the entire infra is critical. Along with this, we would also need an ability to trace end-user request path spanning services - also called Distributed Tracing.

Service Discovery

It does not take much time for our services to grow beyond 100 and at that scale, discovering a service becomes a pain requiring us to put Service Discovery.

3 ways to do it are

  • a central service registry
  • load balancer-based discovery
  • pure service mesh implementation

Authentication and Authorization

Inter-service communication should be secure to ensure that a service does not abuse others; hence we need to put auth in place that allows authorized services to talk to each other.

Config Management

Every microservice has a set of configs, like DB passwords, and API Keys. Committing them to the repository is an unacceptable practice, and we would not want every service to have its own config server.

Hence we need to have a central config management system that is fault-tolerant, robust, and scales well.

No going back

It is extremely difficult to move back to monolith after the teams have tasted microservices. A few reasons would be

  • services are written in various languages
  • teams used to being autonomous
  • teams have adopted new tools and processes

Fault Tolerance

Outages are inevitable and as engineers, we always try to minimize them. A way to achieve this is to keep services loosely coupled that keep outage isolated ensuring no cascading failures.

Internal and External Testing

End-to-end testing becomes complex as it is hard to spin up environments with all services running fine.

Design with Failures in mind

Robust microservices require a counter-intuitive approach, and we need to assume everything would collapse after every line of code. Then we amend the code and architecture to handle it and re-iterate.

Dependency Management is a nightmare

Managing dependencies across services is tough and it leads to a slowdown. The 3 kinds of dependency to be careful about

  • sync dependency on other services
  • services sharing a common library
  • service depending on data coming from other services

Here's the video of my explaining this in-depth ?? do check it out

We always hear great things about Microservices. But, every few months every senior engineer gets a feeling, can we not go back to a simpler time and have monolithic architecture again?

In this video, let's understand the 10 challenges that come with adopting microservices. Today, we would spend time talking about both engineering or tech challenges and organizational challenges that we all should be aware of and address while we adopt microservices.

Outline:

  • 00:00 Agenda
  • 02:34 Managing Microservices
  • 05:25 Monitoring and Logging
  • 08:26 Service Discovery
  • 10:44 Authentication and Authorization
  • 12:17 Configuration Management
  • 14:09 There's no going back
  • 16:56 Fault Tolerance
  • 18:43 Internal and External Testing
  • 20:05 Design with Failures in mind
  • 21:23 Dependency Management is a Nightmare

You can also

Thank you so much for reading ?? If you found this helpful, do spread the word about it on social media; it would mean the world to me.

You can also follow me on your favourite social media LinkedIn , and Twitter .

Yours truly,

Arpit

arpitbhayani.me

Until next time, stay awesome :)

No alt text provided for this image

I teach a course on System Design where you'll learn how to intuitively design scalable systems. The course will help you

  • become a better engineer
  • ace your technical discussions
  • get you acquainted with a massive spectrum of topics ranging from Storage Engines, High-throughput systems, to super-clever algorithms behind them.

I have compressed my ~10 years of work experience into this course, and aim to accelerate your engineering growth 100x. To date, the course is trusted by 600+ engineers from 10 different countries and here you can find what they say about the course.

Together, we will build some of the most amazing systems and dissect them to understand the intricate details. You can find the week-by-week curriculum and topics, benefits, testimonials, and other information here https://arpitbhayani.me/masterclass .

Nagendra Yadav

Senior Python Developer | Django | AWS | Javascript

2 年

Each post is awesome Arpit Bhayani

More about me: arpitbhayani.me Newsletter: arpitbhayani.me/newsletter Subscribe #AsliEngineering for such in-depth engineering concepts: https://www.youtube.com/c/ArpitBhayani Intermediate-Level System Design course: arpitbhayani.me/masterclass Beginner-friendly System Design course: https://www.school-of-programming.com Free course on microservices: https://courses.arpitbhayani.me/designing-microservices All GtiHub Outages: https://courses.arpitbhayani.me/github-outage-dissections/

回复

要查看或添加评论,请登录

Arpit Bhayani的更多文章

  • The best resource does not exist.

    The best resource does not exist.

    This edition of the newsletter contains two quick write-ups about The best resource is mythical Convergent Encryption I…

    4 条评论
  • It's not about what you know, but about how you think

    It's not about what you know, but about how you think

    This edition of the newsletter contains two quick write-ups about It's not about what you know, but about how you think…

    1 条评论
  • Roadmaps are just satisfying your urge to follow a syllabus

    Roadmaps are just satisfying your urge to follow a syllabus

    This edition of the newsletter contains one quick write-up about Roadmaps are just satisfying your urge to follow a…

    3 条评论
  • Always negotiate the offer you get

    Always negotiate the offer you get

    This edition of the newsletter contains two quick write-ups about Always negotiate the offer you get Why PostgreSQL…

    2 条评论
  • Proving your Culture Fit

    Proving your Culture Fit

    This edition of the newsletter contains two quick write-ups about Proving your Culture Fit What not to say during…

    1 条评论
  • Premature Abstractions

    Premature Abstractions

    This edition of the newsletter contains two quick write-ups about Quantify and show impact, whenever and wherever…

    1 条评论
  • Tip the scale in your favor in interviews

    Tip the scale in your favor in interviews

    This edition of the newsletter contains two quick write-ups about How to tip the scale in your favor during interviews…

    2 条评论
  • 7 questions that you should ask your interviewer

    7 questions that you should ask your interviewer

    This edition of the newsletter contains two quick write-ups about Questions that you should ask your interviewers The 4…

    5 条评论
  • Traits of a 10x engineer

    Traits of a 10x engineer

    Build your own Interpreter CodeCrafters launched a super interesting challenge on building your own interpreter. Give…

    3 条评论
  • How PostgreSQL stores data in files, called forks

    How PostgreSQL stores data in files, called forks

    Thank you so much for reading this edition of the newsletter ?? If you found it interesting, you will also love my…

    1 条评论

社区洞察

其他会员也浏览了