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.
Software developers (and not just them) quite often believe that remote work is one of the best things that can happen during their career. Sitting at home or even better, laying on the beach with a laptop on your knees, while drinking some fancy beverage and of course coding from time to time (you’re not at the office anymore, therefore your boss ain’t gonna observe what are you actually doing) pictures like a some kind of dream. But is it really like this?
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!
There are many ways to perform a validation of our models living within the system.
Whether there’s an incoming request from the user who would like to create an account or there’s a need to ensure about the correct amount of money in a bank transaction, the validation process should always (I really mean that) take place. In today’s post, I’d like to present one of the possible solutions that might help you validate your entities.
Although I’m not a big fan of the Autumn (usually a cold weather, rain, not too enjoyable environment to ride a motorcycle and so on), there’s at least one nice thing about this part of the year – a lot of great IT conferences. And one of such is the .NET Developer Days – probably the biggest conference related to the .NET technologies in the whole eastern part of the Europe.
Last time I wrote a post about the commands. Events are quite similar to the commands – the main difference between these 2 patterns is that the events are related to the things that have actually happened to our entity e.g. by invoking the command. They’re also a core part of the DDD (Domain Driven Design) and can be easily implemented within our software solution.
Which one of us doesn’t like to give commands? It’s the natural way to ask (in a polite way) for a specific task that needs to be completed. Therefore, it shouldn’t be surprising that the command pattern can be also easily implemented within our software, which might provide some serious benefits in terms of loose coupling the existing code.
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.
If you take a look at the title of this post and instantly think it’s a trap or bait – let me prove you wrong. This is not going to be one of these catchy titles, so “what kind of bs am I going to read here” has little use in this place. Actually, this is 100% true that contributing to the open source community might greatly affect your life – and it goes far beyond daily activities related to the coding. Therefore, let me tell you a short story about a guy, typical .NET developer, who not so long ago also thought that being an open source developer literally means wasting your time.