As a MEAP subscriber I get the privilege of reviewing some of the new books released by Manning. Some time ago I received Gradle In Action and my review is a bit overdue, so here it is. I’ve been a Gradle enthousiast for the last couple of years, migrating from years of working with Maven, so I was very keen on reading this book.
Spark is rapidly becoming one of my favorite web application prototyping frameworks. Setting up a quick project is extremely easy and plugging in simple templating engines is even easier. It’s being used frequently for teaching other frameworks in order to provide a quick web front-end for that framework (for example, the MongoDB courses use Spark).
But I’ve also used Spark for something else. It’s extremely easy to make a REST prototype with Spark. This way you can make an easy system that can ‘mock’ a future REST backend, but is still adaptable.
How does one change the world? One random act of kindness at the time.
It’s one of my favorite movie quotes and one of the things I try to live by. In our current society, it’s sometimes hard to realize the impact such a random act of kindness makes to another person’s life. I’m not saying it’s an easy thing to accomplish, but it always starts with the littlest of things.
I’ve become a huge fan of CQRS-based codebases due to the fact that such codebases tend to scale really well and are more readable due to the clear boundaries and responsabilities of the components.
When you have a system that’s quite heavy on concurrency (a lot of concurrent system consumers), CQRS will only get you so far. A lot of times such issues can only be solved by either throwing more hardware at the problem or rethinking the way your application handles data. I’ll try to explain to you how you can use an event-based architecture to handle concurrent loads. Mind you, this is a very basic and naive implementation, but it should handle the most common concepts. The code is done in Groovy and Spring 3. It uses Guava’s EventBus to simulate a message bus, one for commands and one for events.
In terms of tenure I still consider myself a rookie in this industry. In some aspects, I’m still an apprentice, in others competent and perhaps one or two area’s proficient (if you don’t know what I’m talking about here, this is based on something called the Dreyfus model). But in my 8 years, I’ve learned a great deal what to do and especially what not to do in order to grow professionally. Here are some of my insights.