You will always need to handle Configuration, State & Logging well

This article is written by our sponsor nautilus2k.com which is a new startup trying to help other startups building data-driven apps on the Microsoft .NET Core/ Azure tech stack.

No matter which technology you use for your tech stack, these are the 3 typical things you will always need to implement for your application. I have done this scores of times myself.

Reactor solves all three problems for you by providing a framework that handles all three aspects in a scalable, secure & performant manner. Having tried out thousands of different ways in which to handle this kind of code, you get the best implementation of all.

Every application needs some sort of configuration to run correctly. Reactor considers configuration as an inherent part of every application and spins up and populates all the necessary configurations at startup using the most reliable, scalable & secure way of storing and reading this information.

So, you get the best mechanism for configuration management on day #1, and you can focus on your business logic, instead of handling infrastructure code.

Configuration should always be stored differently from the state. As an example, when you tell a machine to do something in a certain way, that is configuration. What…