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).
It’s been quite a while since I’ve started gathering some knowledge about the microservices architectural pattern that’s been on a hype recently. After reading many articles, some books like Microservices in .NET Core and talking with smart guys in the Devs PL Slack channel, I’ve eventually decided that the time has come to try to make the microservices happen in the real world project. That’s the beginning of my journey into the distributed programming and architecture, so please keep that in mind while reading this newbie’s post and remember I’d be more than happy to hear your opinions and feedback about the approach that I’m about to present.
It’s been 2 months since the latest version of the Warden has been released as the NuGet packages. Although our focus (yes, I’m not the only one person anymore working on this project) has moved towards the development of so-called stack (brand new API, Website, Microservices etc.) I’m still actively developing the core library in order to make it even more useful than before.
Nowadays, the HTTP APIs act as gateways for petabytes of data and some chunk of it might actually require enhanced access rules. For example, you could create a link that allows the user to download the file only once, and within such link you would find a token.
I was in a need of creating such solution for my open source project Warden – a specialized, one-time link that can be used fetch the configuration object from the API.
It turned out to be fairly straightforward to implement the most basic version of such behavior.
In case you’re not familiar with the Warden project that I’ve been working for the last few months, I strongly recommend you to take a look, as you may find this tool especially useful for monitoring your infrastructure and resources. So what is the Warden Spawn?
It’s a brand new repository within the Warden Stack that will let you configure the instance of the Warden monitoring application using the human readable configuration files – and that’s just the beginning!
Within the last few weeks, a lot of things have happened in terms of the Warden project.
It has gained already quite some popularity and became a whole stack of different applications and technologies with a single, ultimate goal which is providing the unified interface and set of tools to help you monitor and automatically resolve the issues with the maintenance of your system, infrastructure and resources.
18th of June was a very looooong day for me, starting at 4 AM and finishing about 2 AM over 22 hours later. Hours full of joy, emotions, fun, laugh, knowledge and most importantly meeting in person all of these amazing people from the IT community being spread out throughout the whole Poland. 18th of June was the culmination of the Daj Się Poznać 2016 competition, where all of the participants interested in joining this wonderful event have met in the Microsoft office in the Capital City of Warsaw.
Hey, do you remember one of my latest posts in which I’ve described how easy it is to integrate the C# with Slack? I’ve taken this concept a little bit further and created a new type of integration which can do pretty much the same thing but in a more sophisticated way in terms of configuration and available options. So, are you ready to integrate your Warden with the Slack?