🔥The 9th Round of Easy Loan, Earn $40 Reward is in progress❗️ ⏰ Promotion Period: January 15th - Feburary 15th, 2025 👉 Register now and check more details at gate.io/campaigns/358

Microservice architecture adoption anti-pattern - Microservices as the goal bit.ly/2Db1jqG

What's a (micro)service - part 1? bit.ly/2ScrFN9

Documenting a service using the microservice canvas bit.ly/2tIa06m

Oh dear: According to Gartner 70% of the IT market is focusing on DevOps and another study found that 88% of organizations have adopted agile, but only 26% of organizations have broadly adopted test automation.

Managing data consistency in a microservice architecture using Sagas part 2 - coordinating sagas using choreography or orchestration bit.ly/2KiOb6F

Key lessons: 1. Be very, very careful when using shared libraries that contains 'unstable business rules' in a microservice architecture. 2. More generally ensure your services encapsulate change rather than having changes regularly impact multiple services 1/n

Learn-Build-Assess microservices: book, patterns, articles, presentations, example code, training classes and consulting, assessment platform, ... microservices.io/adopt/index.ht…

Coarse-grained microservices - Service per team Pattern bit.ly/35jOCFa

Just a reminder: picking the appropriate architecture for your application is a best practice. microservices.io/patterns/index… changelog.com/posts/monolith…

I'd propose no-prefix services: no microservice, no macro, no mini. Just a service. microservices.io/patterns/decom…

“Neither monoliths nor microservices are the future," says "Microservices Patterns" author Chris Richardson "They’re essentially patterns, and your job as an architect is to understand the context in which you are working, the problems you need to solve, and then pick the appropriate

Decompose your monolith - ten principles for refactoring a monolith to microservices bit.ly/2YrkDua

Message brokers aren't designed to efficiently transport large messages: you should send a message containing a pointer/URL instead. Twitter is the same. Attempting to express a complex idea in a tweet is likely to fail. It's best to share a link to a longer post.

One of the defining characteristics of the microservice architecture is that services are independently deployable. But there's more to this definition than simply packaging a service as a WAR or executable JAR that can be built and deployed independently of other services.

One of the most interesting things I've read this year was the research paper by Adam Tornhill that described how organizations waste up to 42% of their time due to technical debt. It's extremely valuable to see a study that quantified the consequences of technical debt.

Monolith First is generally good advice. But it's not universally applicable. Sometimes it might make sense to start with microservices. To understand why, let's analyze the trade-offs using dark energy and dark matter.

The essence of applying the Microservice architecture pattern is defining the service architecture: identifying the services, defining their responsibilities, their APIs and their collaborations (with other services).

One key dark energy force that shapes an architecture is team autonomy. Team autonomy is the ability of a team to make decisions and take actions without the need for approval from other teams. It's critically important for rapid, frequent, and reliable software delivery

The core idea of the success triangle is that the rapid, frequent, reliable and sustainable delivery of software requires three elements: DevOps, Team Topologies, and an architecture that enables them.

One of my favorite presentations is my #QConPlus 2021: talk: Takeout burritos and minimizing design-time coupling in a microservice architecture. Creating the presentation was challenging. I felt hungry whenever I looked at the pictures, especially in the AM.