These days dunking on #Microservices is getting easier, so I did it. I provided my rational take on how to (not) cut your system into microservices.

Pracując z klientami jako konsultant i architekt zauważam, że o ile większość moich rozmówców ma świadomość jak zbudować system oparty o mikrousługi, o tyle gdy przychodzi temat raportów i szeroko pojętego Business Intelligence to sprawy mają się różnie. W tym wpisie chciałbym pokazać z jakimi najczęściej wdrażanymi rozwiązaniami się spotykam, jakie mają wady/zalety oraz jak można to zrobić lepiej używając oczywiście chmury

Outbox pattern is simple, yet powerful tool. Let’s see how does it work and what are the consequences of applying it. With outbox, instead of sending a message over the wire to message broker, we save a message to our microservice database as part of current business transaction. This way we achieve internal consistency inside our service. No messages will be sent if a transaction is rolled back...

In this article we are going to show you how you can combine SignalR and RabbitMQ to build real time server-client communication. We will extend our insurance sales portal with chat service. This chat will let insurance agents communicate with each other. We also will use this chat service to send users information about certain business events like new product availability, successful sale or insurance product or tariff changes.

In this article we are going to focus on another fundamental concepts of microservice based architecture – api gateways.

In this article we are going to focus on service discovery, which is one of the fundamental concepts of microservice based architecture. Service discovery is a mechanism that allows services to find each others network location. There are many possible implementations of this pattern, but in this article we will focus on implementation that consist of Service Registry component and Service Registry Clients.

I liked .NET technology from its inception. In fact I left the dark star of overxmlized J2EE development to join forces of rebellion around 2004. Over the years my team here at Altkom Software & Consulting built and maintained more and more complex business solutions for insurance and banking. While Java was in stagnation .NET platform developed very quickly. We wanted to find out possible options for dealing with typical microsevice related tasks like service discovery, service communication synchro...

Temat mikroserwisów w świecie IT jest ciągle żywy. Jak każda nowość – generuje dużo szumu i wzbudza wiele kontrowersji. Jeszcze do niedawna rozmowy o architekturze mikroserwisowej dotyczyły tylko i wyłącznie backendu aplikacji. Przestarzały, nielubiany i krytykowany przez wielu monolit spychany był w stronę warstwy prezentacji. W pewnym momencie zaczęto się zastanawiać – czy coś nam zaraz nie wybuchnie?

I think its no secret that more and more development teams are trying to take more of a micro service oriented approach (and for all the good reasons). With the power that cloud providers give plus the benefit of container (Docker and Kubernetes) I think it is inevitable that micro services will become a standard. Of course this approach is not problem proof but it allows us to move some of the monolith type application issues somewhere else where we have more flexibility

My review of "Building Microservices" book by Sam Newman - a great compendium of microservices architecture.