Free AI web copilot to create summaries, insights and extended knowledge, download it at here
7719
Abstract
icroservices architecture back to a monolithic architecture</a> due to this very complexity.</p><p id="deff">Well, here are some personal thoughts :</p><ol><li>Managing numerous independent services can be daunting, requiring sophisticated solutions for issues like service discovery, load balancing, and inter-service communication. These elements need careful coordination and advanced tools to ensure seamless operation, which can increase the difficulty of managing the overall system.</li><li>Maintaining data consistency across multiple services can be difficult, and distributed transactions, while theoretically possible — are complex and often discouraged in a microservices setup. This can lead to data integrity issues if not handled correctly.</li><li>Deploying and monitoring a large number of services necessitates the use of advanced tools and practices. Continuous integration and continuous deployment (CI/CD) pipelines, service meshes, and centralized logging are critical to manage these tasks effectively. However, setting up and maintaining these tools can be resource-intensive</li><li>Communication between microservices over a network introduces latency, which can negatively impact performance. Also back to my point of #2, the data transfer and storage costs are also hidden in solutions of this nature.</li></ol><div id="dce3" class="link-block">
<a href="https://amzn.to/4cZRKcz">
<div>
<div>
<h2>Building Microservices: Designing Fine-Grained Systems</h2>
<div><h3>Building Microservices: Designing Fine-Grained Systems [Newman, Sam] on Amazon.com. FREE shipping on qualifying…</h3></div>
<div><p>amzn.to</p></div>
</div>
<div>
<div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/0*KsAS-Lf5SZ6ZEvMH)"></div>
</div>
</div>
</a>
</div><h1 id="2c26">The landscape of Microservices is evolving</h1><p id="24aa">As we evaluate the state of microservices in 2024, several trends and technologies have emerged. Here’s my personal summary of some key trends that influence the relevance of microservices:</p><ol><li><b>Kubernetes and Containerization</b>: The rise of <a href="https://cloudmelonvision.com/what-is-kubernetes-really-about/">Kubernetes</a> and <a href="https://cloudmelonvision.com/getting-started-with-devops-containers-and-kubernetes/">containerization</a> has made deploying and managing microservices more straightforward. Kubernetes provides robust orchestration capabilities, simplifying the deployment, scaling, and operation of containerized applications.</li><li><b>Serverless Architectures</b>: <a href="https://cloudmelonvision.com/things-you-didnt-know-about-serverless/">Serverless computing</a>, where developers focus on writing code without worrying about the underlying infrastructure, has gained popularity. Services like AWS Lambda, Azure Functions, and Google Cloud Functions allow developers to build and deploy functions as microservices. This approach reduces operational overhead and can complement microservices by handling specific tasks.</li><li><b>Service Mesh</b>: Service mesh technologies, such as Istio and Linkerd, address many of the networking challenges associated with microservices. They provide features like load balancing, traffic management, and security, simplifying the management of inter-service communication.</li><li><b>Observability and Monitoring</b>: Enhanced <a href="https://cloudmelonvision.com/ranking-top-5-logic-app-monitoring-tools/">observability tools</a> have become essential in managing microservices. Solutions like Prometheus, Grafana, and Jaeger help monitor, trace, and visualize the behavior of microservices, providing insights into performance and aiding in troubleshooting.</li><li><b>API Gateways</b>: API gateways play a crucial role in managing traffic between clients and microservices. They offer features like request routing, rate limiting, and security, ensuring smooth communication and protecting the backend services.</li></ol><blockquote id="6556"><p>organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations<i>. — By M. Conway — <a href="http://www.melconway.com/Home/Conways_Law.html">Conway’s law in 1968</a></i></p></blockquote><div id="9210" class="link-block">
<a href="https://aws.plainenglish.io/navigating-the-cloud-native-landscape-a-glimpse-into-kubecon-europe-2023-17ce4dfc21d7">
<div>
<div>
<h2>Navigating the Cloud-Native Landscape : A Glimpse into KubeCon Europe 2023</h2>
<div><h3>KubeCon has long been my one of favorite events in the community, and this year’s KubeCon + CloudNativeCon Europe 2023…</h3></div>
<div><p>aws.plainenglish.io</p></div>
</div>
<div>
<div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/0*gZcMCbwOsok0cCnt.png)"></div>
</div>
</div>
</a>
</div><h1 id="8f26">Decoding real-life microservices architecture</h1><p id="91dd">As <a href="https://docs.microsoft.com/en-us/azure/architecture/microservices/index">Microsoft defines</a>, a microservices architecture is a system that contains a collection of small, autonomous services. So, let’s walk through and decode a real-life microservice architecture.</p><h1 id="e512">Key principles in action</h1><p id="74da">Here are some principles that I summarized to follow when deploying microservices on Azure:</p><ul><li>One app server per microservice.</li><li>Each microservice has its own data persistent store (backend).</li><li>Each microservice has an independent life cycle.</li><li>No dependency on other modules.</li><li>Small and numerous microservices facilitate fast and frequent deployment.</li><li>Strongly loosely coupled, acting as small elastic units within the distributed system.</li><li>Isolation from the resources of other applications.</li></ul><p id="6384">The direct outcome of this philosophy looks like this :</p><figure id="f183"><img src="https://cdn-images-1.readmedium.com/v2/resize:fit:800/0*BoQnlWWREiUQOdgP.png"><figcaption></figcaption></figure><h1 id="8873">My personal analysis</h1><p id="1ec8">You see, modern cloud-native applications designed for microservice architecture should be managed in a version control tool like Git, following the principle of “a codebase = 1 repository.” This shows dependencies and systems should be isolated and declared explicitly and independently to facilitate maintenance and administration tasks.</p><p id="e68d">Additionally, code should be separated from configuration files, meaning that code should contain only variables and not application or environment settings. The application should be strictly stateless, with each module sharing nothing with others. Generally, the front end does not store any data. instead, data is always in the backend, possibly exchanged through middleware such as RESTful APIs.</p><p id="e75d">Each application must be autonomous and <b><i>self-contained</i></b>, adhering to the principle of “<b><i>one process, one microservice.</i></b>” This approach allows microservices to be well-structured, making it easy to add or delete processes. During peak times, processes can be scaled by increasing instances, and during downtime, services can be rapidly stopped and started, ensuring a quick return to normal operations.</p><p id="9426">Checking the integrity of event and flow logs is crucial when implementing a monit
Options
oring strategy. Since each microservice operates independently but functions as part of a whole system, log implementation should be event-based. Microsoft Azure provides log analytics services and other metrics for monitoring each microservice effectively. Sounds a bit complex right? Let’s take a look at a prime example of microservices!</p><div id="fa01" class="link-block">
<a href="https://aws.plainenglish.io/what-i-wish-i-knew-when-i-got-started-with-kubernetes-177cf717f5ef">
<div>
<div>
<h2>What I Wish I Knew When I Got Started with Kubernetes</h2>
<div><h3>Get acquainted with the key things you need to know to get started with Kubernetes, through hands-on practice.</h3></div>
<div><p>aws.plainenglish.io</p></div>
</div>
<div>
<div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/1*Pt4bR0zjJIZyi4d962_cIg.png)"></div>
</div>
</div>
</a>
</div><h1 id="29b0">A prime example of microservices: e-Shop</h1><p id="8e1e">One of the most interesting parts of the workshop analyzes a real-life example built with microservices on Azure called <a href="https://github.com/dotnet/eShop">eShop by Microsoft</a>. This is a microservice architecture-based application that implements an e-commerce website using a services-based architecture with <a href="https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview">.NET Aspire</a>.</p><div id="eafe" class="link-block">
<a href="https://github.com/dotnet/eShop">
<div>
<div>
<h2>GitHub - dotnet/eShop: A reference .NET application implementing an eCommerce site</h2>
<div><h3>A reference .NET application implementing an eCommerce site - dotnet/eShop</h3></div>
<div><p>github.com</p></div>
</div>
<div>
<div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/0*2OMwW_dNGu2ziEd3)"></div>
</div>
</div>
</a>
</div><p id="4db6">This project contains different types of microservices and can be managed by API gateway:</p><figure id="29e1"><img src="https://cdn-images-1.readmedium.com/v2/resize:fit:800/0*Ie6-7U_7AM-USzqA.png"><figcaption></figcaption></figure><p id="0451">Although the orchestration layer is more complex, so the overall systems that you could read from above principles lead the final architecture looks like this :</p><figure id="e601"><img src="https://cdn-images-1.readmedium.com/v2/resize:fit:800/0*CyWeHbTWiDkhAa4N.png"><figcaption></figcaption></figure><p id="a848">If you’re a .Net developer or anyone who is experienced in Microsoft technical solutions, you would definitely benefit from one excellent book that is recommended by Microsoft : <a href="https://aka.ms/microservicesebook"><b><i>.NET Microservices Architecture for Containerized .NET Applications.</i></b></a><b><i> </i></b>This book explains in detail how to develop the microservices architectural style and set up the golden stamps of microservices.</p><div id="d6b3" class="link-block">
<a href="https://dotnet.microsoft.com/en-us/learn/dotnet/architecture-guides">
<div>
<div>
<h2>.NET Application Architecture Guides</h2>
<div><h3>Free e-books and practical advice for developing for web, desktop, mobile, and microservices with Docker.</h3></div>
<div><p>dotnet.microsoft.com</p></div>
</div>
<div>
<div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/0*-HOBCuKlHpRdmsoU)"></div>
</div>
</div>
</a>
</div><h2 id="b1de">Are Microservices here to stay?</h2><p id="82f8">As we look towards the future, several factors will determine the continued relevance of microservices beyond 2024. <a href="https://cloudmelonvision.com/navigating-the-cloud-native-landscape/">Cloud-native technologies</a> such as <a href="https://cloudmelonvision.com/if-i-were-about-to-get-started-on-kubernetes-in-2024/">Kubernetes</a> and <a href="https://cloudmelonvision.com/decoding-serverless-kubernetes/">serverless</a> are still going strong, and their emerging with technologies like AI and machine learning, leading to smarter and more adaptive systems. And in this emerging section, <a href="https://cloudmelonvision.com/ranking-top-5-logic-app-monitoring-tools/">AI-driven monitoring</a> and self-healing capabilities will further enhance the robustness of microservices architectures.</p><p id="7a86">Please also don’t forget the rise of edge computing, where data processing occurs closer to the source of data generation, will complement microservices by enabling low-latency, real-time applications. Above all, as regulatory requirements evolve, microservices architectures will need to incorporate robust security and compliance measures, with solutions that provide seamless integration of security protocols.</p><p id="8ba7"><b><i>It’s almost a no-brainer that Microservices will continue to stay!</i></b></p><p id="7e27">Improving the developer experience is needed. Tools and frameworks that simplify development, testing, and deployment will encourage adoption and innovation.</p><div id="9056" class="link-block">
<a href="https://pub.towardsai.net/gpus-kubernetes-decoding-next-gen-ai-enabling-workloads-00d7a1f104ae">
<div>
<div>
<h2>GPUs + Kubernetes =? Decoding Next-gen AI-enabling Workloads</h2>
<div><h3>Cloud-native technologies such as Kubernetes and serverless have been revolutionizing modern application design and…</h3></div>
<div><p>pub.towardsai.net</p></div>
</div>
<div>
<div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/1*YxDPxAlzZyZx8dZ29GgwLw.png)"></div>
</div>
</div>
</a>
</div><h1 id="e026">Looking forward</h1><p id="cee0">Personally, I greatly enjoyed the latest deployment methods and creative styles in designing application architecture brought by cloud computing. Cloud computing is boosting our business today. If you like reading stories like this, if you enjoy similar topics, you can follow me <a href="https://www.youtube.com/@CloudMelonVis?sub_confirmation=1">on my YouTube channel</a> or follow me <a href="https://melonyqin.com">@melonyqin here on Medium</a> and subscribe to <a href="https://newsletter.cloudmelonvision.com">my newsletter</a>. See you in the next one! Thanks for your continued support. Let’s stay tuned!</p><h1 id="d2e2">In Plain English 🚀</h1><p id="07aa"><i>Thank you for being a part of the <a href="https://plainenglish.io"><b>In Plain English</b></a> community! Before you go:</i></p><ul><li>Be sure to <b>clap</b> and <b>follow</b> the writer ️👏<b>️️</b></li><li>Follow us: <a href="https://twitter.com/inPlainEngHQ"><b>X</b></a> | <a href="https://www.linkedin.com/company/inplainenglish/"><b>LinkedIn</b></a> | <a href="https://www.youtube.com/channel/UCtipWUghju290NWcn8jhyAw"><b>YouTube</b></a> | <a href="https://discord.gg/in-plain-english-709094664682340443"><b>Discord</b></a> | <a href="https://newsletter.plainenglish.io/"><b>Newsletter</b></a></li><li>Visit our other platforms: <a href="https://cofeed.app/"><b>CoFeed</b></a> | <a href="https://differ.blog/"><b>Differ</b></a></li><li>More content at <a href="https://plainenglish.io"><b>PlainEnglish.io</b></a></li></ul></article></body>
