During the last days, I dug a little bit into the Saga pattern. The Saga pattern is an architectural pattern which provides an alternative approach to big and long-running ACID transactions. It takes a business process and breaks it down into small isolated steps - each of them with its own transaction. The overall consistency is provided by manually reverting past actions if needed (called compensating).

During the last couple of months, I wrote a lot of blog posts about ActiveMQ, AngularJS and Spring. Most of those blog posts include some small code snippets, but nothing more. That’s why I decided to make a boilerplate project to show how all those different techniques can go hand in hand in a bigger example.

Generating PDFs can be a tricky job. If you ever worked with templating engines like Jasper you probably know what I mean. On the other side, HTML makes it extremely simple to describe documents. So why not use HTML to generate PDFs?

No matter what type of software you make, there will always be errors. There might be bugs in your code or an external system is just down at the moment. No matter what, it will cause you trouble.

A couple of days ago I published a post about the difference between queues, topics and virtual topics. Today I want to share some practical information on how to use virtual topics in ActiveMQ with Spring Boot.

ActiveMQ provides a variety of different messaging patterns. While queues and topics are the most known ones, virtual topics can combine the best of both worlds: multiple consumers with their own dedicated queue.

The following example shows how we can use Google’s ReCaptcha for an anonymous login and authentication with JSON Web Token.

Roughly about two years ago, I wrote an article called “Why using Spring’s @Value annotation is bad”. I described why you should avoid the @Value annotation in your code and prefer @ConfigurationProperties:

Yesterday, I received an e-mail from a reader of my blog. He told me that he clicked on the XING link on my “About” page, but was redirected to some shady online trading website instead of my XING profile. So I took my laptop and took a look at it. And - to my surprise - he was right! I started to investigate what was going on. Here’s what I found out.

Most of the time, testing AngularJS applications means testing JavaScript. We test services and we test controllers. But what about directives? What about components? How do we test compiled and injected AngularJS code?