9 Years of code
I wrote my first hello world in Java in 2012, at the university. And I want to share few thoughts that I have changed over these years.
I wrote my first hello world in Java in 2012, at the university. And I want to share few thoughts that I have changed over these years.
In the last few months, I have been learning about the minimalism movement for a while and I will like to share some thoughts about this.
Sometimes we deal with well-secured scenarios where there are no many ways to check HTTP traffic. And in these cases, common tracing tools are not enough.
Consider the next communication:
In our society, we could say that money is equal to power. Because with money you have the power to buy things or services. But that is not actually all.
What does really money means nowadays? In essence, since the fall of the gold standard, caused by the Nixon shock in 1971, money now is just a portion of debt. That’s it, for the last 50 years, a paper that means that you have a representation of a debt.
There are some scenarios where we don’t need to wait for fast feedback when executing tasks. In some cases, we can just request the computation of that a task, a command, and at some moment in the future, we can receive a callback notification with the execution result.
To explore a solution for this posibilities, I decided to build this example by applying an asynchronous command queue.
We can discuss a lot about what is or what is not Event Driven Architecture. But in this post, we will see how events can improve the design in our solutions.
In some applications, we can find many benefits by splitting the model into two parts: the update part, commands, and the reading part, queries. In 2006, Greg Young started talking about this pattern, also known as Command Query Responsibility Segregation (CQRS).
What is this architecture about, and what`s the difference from others more traditional like MVC?
If we go back to 2005, according to Alistair Cockburn, the creator of this term, this architecture tries to solve the problem of Avoid infiltration of business logic into the user interface code.
The most important thing of this architecture is to protect the most valuable code of any application, the domain.
Be the worst is about learning, and to have people about to learn from.
Maybe you are better than someone in some at some area, but that doesn’t mean you’re better than him. Someone may be much better than you at something, that does not mean that you are worst than him.
HTTP provides some authentication schemes like: Basic, Bearer, Digest, HOBA, Mutual, Negotiate, OAuth, etc. As described in the RFC.