Home Cloud 8 Architectural Considerations to Keep in Mind About Microservices

8 Architectural Considerations to Keep in Mind About Microservices

by Vamsi Chemitiganti

This week, I’m honored to have a guest post from my friend, colleague & Cloud Thought Leader – Bich Le, Co-founder and Chief Architect at Platform9 (https://platform9.com/leadership/) . Bich has a super insightful post on “8 Architectural Considerations to Keep in Mind About Microservices”. Bich is a deep thinker and doer much like his co-founders at Platform9.

What has always astounded me about Bich is the originality & depth of his work on disruptive innovation.

In this blog, he talks about the eight considerations enterprise architects should keep in mind while designing microservices architectures, namely –

  1. Increase Agility as well as aim to achieve higher density
  2. Consider Form Factor for Digital Applications
  3. Don’t forget the Orchestration Layer
  4. What about the Triggering Mechanisms
  5. A unified Logging and Tracing strategy is an enterprise “must have”
  6. Monitoring, Metrics Collection, and Performance Across Microservices
  7. You cannot sacrifice State – Data Services
  8. Accelerate Time-to-Value and Simplify Ops with Serverless

Please click on the image or the link below to access the full article.

Over the past several years, the use of microservices as a means of driving agile best practices and accelerating software delivery has become more and more commonplace. In an effort to avoid the pitfalls that come with monolithic applications, microservices aim to break your architecture into loosely-coupled components (or, services) that are easier to update independently, improve, scale and manage.

We see organizations of all sizes, including large enterprises, looking to take advantage of microservices, containers, serverless and other modern architectures — both for greenfield applications, as well as for de-composing their monolithic, legacy applications.

However, as you can imagine, these massive architectural changes do not happen overnight, and have broad implications — from the way you develop, deploy, manage, and monitor your application, through your organization’s culture, team structure, skill set, and more.”

How can you make microservices an integral part of your development and software delivery strategy? Here are eight things to keep in mind as you’re planning for microservices.

8 Architectural Considerations to Keep in Mind About Microservices

Discover more at Industry Talks Tech: your one-stop shop for upskilling in different industry segments!

You may also like

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.