It’s been a few months already since I’ve started working for good with distributed systems using (micro)services and asynchronous processing via service bus. Many issues and question raised and one of these was how to not lose the information about commands and events being processed and even more importantly, how to notify the user once the request has completed? I’ve had to come up with some solution that seems to be sufficient (at least for now) and I’d like to share it with you.
Welcome to 2017 my dear folks! New year, new me – right? Not entirely correct, as I’d rather paraphrase this sentence to sound more like “new year, new projects (and tons of new code)”. Wondering what I’d like to achieve within the next 365 days (or make it 364 to be precise)?
Time goes by whether you like it or not (unless you’re a photon). So is 2016 about to finish – the year that was one of the biggest breakthroughs not only in my career but also in life so far.
It’s been quite a while since I posted the latest update of the Warden project designed for monitoring the resources in general. After a lot of back-end coding and refactoring, the time has come to finally focus on the new web interface implementation. And this is where the things start to become interesting (I promise).
Writing a project documentation – everyone’s or at least the programmer’s nightmare, right? Although at a first glance many of you will most likely agree with the given assumption, I’ll try to convince you otherwise. Not only it doesn’t have to be a dull experience, but it might be a truly fun and quite refreshing activity, which shall provide the great value for the project.
Necessity is the mother of invention – that’s basically why I did create a new open source project called Lockbox. Its main purpose is to provide a centralized and secured storage for the application settings that can be easily fetched via HTTP request. Sounds interesting? Then let me guide you through the most important concepts of the Lockbox.
Not so long ago, I’ve eventually decided to dive into the world of microservices.
I did look for an opportunity to make use of this architectural pattern for quite some time and finally was able to do so.
After 3 months of trying out the new things and learning stuff mostly on my own (the hard way) I believe it’s a good time to share some of my experience. I have no doubts that at some point in the future when I look back at this post I might be like – “oh God, what was I thinking back then, it’s so wrong”, but well, let me show you what did I learn so far and maybe you won’t repeat some of my mistakes.
When was the last time that you did something that you weren’t supposed to do? And I’m not talking about committing the criminal acts. Although, at the first glance it might seem otherwise, making uncomfortable things most likely will pay off.
Yet, still, most of us decide not to leave the comfort zone.
Fortitudo 42.do is an advanced application for tracking your training progress.
At first, we released just an Android application and it’s been the only platform supported for quite some time now, but from today on everything changes – you can use a brand new, responsive web application that will help to achieve your fitness goals!
When someone talks about the diversification, it’s usually about financial assets. Every investor will tell you, that you should spread your investments amongst different sources of possible income. If you put 100% of all that you’ve got into a single asset and something goes wrong then you’re totally screwed. Yet, it’s not only about the financial market – let’s talk about diversifying our own skills.