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.

Z racji tego że to okrągły, 16 post, to postanowiłem zrobić coś nowego :). Obecnie mój blog jest wypełniony ciężkimi, technicznymi tematami. To zawsze będzie serce i kręgosłup tego bloga. Jednak, aby zachować świeżość umysłu, trzeba od czasu do czasu zrobić coś nowego. Postanowiłem podzielić się opinią o książce “Building Microservices with ASP.NET Core” autorstwa Kevina Hoffmana. Książka ta jest stosunkowo nowa (wydana w tym miesiącu) i w momencie pisania tego artykułu nadal utrzymuje się wśród nowości ...

Microservices are still pretty popular in our industry since they imply lots of benefits. However working with that kind of architecture might be annoying when it comes to commit the changes using GIT. Why? Simply because in a common approach, each microservice should be put in a separate repository. Therefore, instead of doing your typical „GIT sequence” once, you end up with few terminals where you do pretty much the same job. Fortunately, you can avoid that with no big deal. ...

I often work on applications whose sole task is to execute a script at certain time or day. You may approach it in several ways, eg.: Task Scheduler (Windows), SQL Job (if it is a SQL task) or CRON in Linux. You may also write application, which would run in background and execute a script at certain time. The only question is – do you really want do it? In this post, I would like to introduce other solution to tasks like this. ...

It’s been quite a while since I’ve started gathering some knowledge about the microservices architectural pattern that’s been on a hype recently. After reading many articles, some books like Microservices in .NET Core and talking with smart guys in the Devs PL Slack channel, I’ve eventually decided that the time has to come to try to make the microservices happen in the real world project. That’s the beginning of my journey into the distributed programming and architecture, so please keep that in mind wh...

Jak wybrac losowy port do hostowania np. mikro serwisu? Jaki zakres portow wybrac? Jak sprawdzic, czy port jest wolny?

MiSeCo #8: Service discovery methods ?>michalComments 0 Comment This is an 8th post in a series about MiSeCo – a project I am working on for the “Daj się poznać” challenge (in Polish). So far I have implemented a way of calling service methods remotely over HTTP protocol. Currently, service URL is hard-coded in the application. I need to find a way to allow services register automatically so that very little configuration is needed. Initially, I wanted to create MiSeCo in the way that there is no c...