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.
Reactor, our hyper-scalable data source is the core component of our development framework. Let me explain why Reactor is a game changer and why you need it.
At the outset, it was apparent to me that the key to simplifying code for data-driven applications was by creating a data source that could return the data you need effortlessly, without compromising scalability or performance.
If we could build a data source like that, then no matter where the data comes from, or how much data was stored in the backend, developers would easily be able to read what they wanted to without having to worry about anything except their business logic.
Let us consider a typical scenario where you have a firm, office, and rep where a firm can have multiple offices, and each office had a few reps.
In most such scenarios, the DBA would be giving you one query to read all that data in one go. And we all know that such queries all over your code base become a scalability problem that becomes harder and harder to solve as you become successful.
