Builder pattern to gain object immutability is the most commonly used solution. I analyze its advantages, disadvantages and alternatives based on a real-life example.
In the first two parts of the series about messaging (1 , 2) I made a certain inventory of concepts. Now, I am about to mix them up and show the usage with the help of SNS <-> SQS implementations.
Nowadays, we all create microservices and more and more often we use asynchronous communication. In the first article from the series, I wrote about message construction and messaging channels. Here, I will focus on message routing and endpoints.
Nowadays, we all create microservices and more and more often we use asynchronous communication. In this article, I will try to identify the individual elements of such a messaging system and their roles. In the first part I will focus on message construction and messaging channels.
We all know that immutability is GOOD. But should we use it everywhere by default? Let’s show it on the basis of a distinction between Entities and Value Objects.
This article discusses different approaches to creating a layered architecture – how to reflect the business context in the code; how to structure it; how to understand the dependency inversion and infrastructure layer; and finally as a possibly isolate modules.
The mental model of object-oriented programming is not intuitive. The speed and dynamics of today’s data-centric world make it a difficult case. How to learn object-oriented programming then?
Tech Jump is the pilot of mentoring program in Schibsted Tech Polska – Academy project. The idea is to allow people to switch the technology or just to get to know another one.
Yes, there are some reasons to use the Java framework Vaadin. But there are many more disadvantages in my opinion.