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.
I’m calling it the Reactor model, the naming being influenced by the Actor model. The Reactor is a hyper-scalable, high-performance data source that sits in front of your relational database (which you still need for storing important data which requires data integrity & consistency).
Having a reactor in your topology enables you to create high-performance apps and powerful cloud services with natural, intuitive code where developers can focus on implementing business logic as-is, without having to code around database scalability concerns.
Why is it so hard to implement business logic?
Because developers often forget the primary requirement while trying to get the database schema and query performance right. They also push back and prevent you from implementing the requirements as-is.
You can easily upgrade your system over time to use a Reactor for all data reads. Actors can use Reactor as the default data source.
v1 had an inconsistent performance. v2 consistently gives 100% better performance than conventional methods. v3 which I am currently working on is expected to take things to a…
