rugger
Joined 19 years ago
Joined 19 years ago
That's why I mentioned Event Sourcing pattern, not "microservices". Think of a single event log as a source of truth where all the data goes, and many consumer processes working in parallel alongside, picking only those events (and the embedded data) that concern them, reacting to them, then passing it on not knowing what happens later. Low coupled small self-sufficient components that you can keep on adding one next to another, without increasing the complexity of the overall system.
Maybe Event Sourcing/CQRS can be called "microservices done right", but that's definitely not those microservices (micro-monoliths?) everyone is talking about.
But when you start adding business rules, and start transforming your data and moving it around, then your monolith will become too complex and often too expensive to run. Lots of moving parts tightly coupled together, long-running transaction wrapping multiple joined tables etc. Rolling out new features will become very challenging as well.
Something like event sourcing is more complex to set upfront than a monolith, but at least it offers the way to add scale and features later without creating a combinatorial explosion...
From the author of the Sequel gem. It can do everything that Rails can, faster and lighter by order of magnitude, expandable (turn on only the plugins you need), and it does it all 'the Ruby way', not 'the Rails way'. That means simplicity, clarity and power. Generally, all software Jeremy Evans releases is of excellent quality and actively supported. Oh, and this Roda framework is in active use by the US government and is subject to regular security audits...
The definition of obscure but powerful and quite beautiful web framework.