chamod udara’s Post

Point-to-point and publish/subscribe are two common communication techniques for #microservices. But which one is more effective for your system as you transition from a monolith to microservices? 👉 Point-to-point communication is often synchronous, with a designated sender and receiver using HTTPS or gRPC calls to facilitate two-way dialogs. On the other hand… 👉 Publish/subscribe is usually asynchronous and can offer a more scalable and resilient option. This is often achieved through real-time stream processing platforms like #ApacheKafka, which adds a layer of indirection, reducing coupling, and allowing for scalability. 📺To learn more about the strengths and limitations of these communication techniques, check out Wade Waldron’s new Microservices 101 video. Watch it here ⬇️

As a software leader, I admit to have jumped on the microservices architecture bandwagon...even worse, for a while I was drinking the MACH Koolaide. Microservices have become so granular that they are often hard to identify in your running application. In fact I recently heard a client commenting about an eCommerce composable offering as just being a "bucket of API's". As it turns out, we are solving one complexity problem with another type of complexity. So if monolithic is a thing of the past and microservices will become a governance nightmare; what's the answer? As always the answer is somewhere in between...more on that on my next post.

🚀 "Decoding Microservices: An Introductory Overview" Dive into the dynamic world of microservices! This article covers everything from basics, benefits, and challenges, to best practices. Perfect for anyone in software development looking to stay ahead of the curve. 🔗 Read, learn, and share your thoughts! https://lnkd.in/dgyv3qN9 #microservices #softwareengineering #techtrends #mediumarticle #softwaredevelopment #softwarearchitecture

Questioning your knowledge is important! In many articles and books, "Microservices" and "Distributed Systems" are used interchangeably. Are they? I want to know from you: ➡️ Can a Microservice be a non-Distributed System? ➡️ Can a Distributed System not be based on Microservices? #microservice #softwarearchitecture

What do you do when your Modular Monolith grows and starts hurting you? Identify modules that: - Are changed frequently - Generate high traffic - Are increasing heavily deployment time - Are increasing the risk of failure You can consider extracting them to microservices. This means that in your application you would deal with the following: - Modules that are still inside Modular Monolith - Modules that were extracted to microservices Theoretically, each module can be extracted to a separate microservice (1 microservice = 1 module). In practice, sometimes it makes sense to put 2 (or more) modules in 1 microservice together: - One of the modules is talking often with another one - The module is tiny This way, you can omit problems related to network errors or latency (between these modules). And what is your experience on that topic? #softwarearchitecture #softwaredevelopment

Point-to-point and publish/subscribe are two common communication techniques for #microservices. But which one is more effective for your system as you transition from a monolith to microservices? 📺 Check out this Microservices video and learn more about the strengths and limitations of these communication techniques. ⬇️

Point-to-point and publish/subscribe are two common communication techniques for #microservices. But which one is more effective for your system as you transition from a monolith to microservices? 📺 Check out this Microservices video and learn more about the strengths and limitations of these communication techniques. ⬇️

In recent times, we've transitioned from monolithic to microservices in application development, and APIs now play a crucial role in facilitating communication between microservices. Join us for our upcoming #ApplicationSecurity webinar to learn more about this topic. https://bit.ly/3zQdtW7

Discover how Microservices Architecture boosts development speed, scalability, and maintainability by breaking apps into independent services with lightweight APIs. Learn best practices to tackle network challenges like latency and build resilient systems: https://lnkd.in/diSY8E6p Video by Fernando Doglio

Microservices have been around for quite a while, but there still is some confusion about what they're all about. First and foremost, they are an implementation pattern, meaning that from the outside of a system, you cannot tell whether they are used or not. 🎥 APIs and Microservices: What's the Difference? - https://lnkd.in/e_H52a_r #api #apimanagement #microservices #softwarearchitecture #architecture #apistrategy #digitaltransformation Getting APIs to Work