Article omits significant Saga pattern issue: every implementation is unique and tedious, can't be abstracted out to library/framework and, like Circuit Breaker, intermixed with business logic.
Peter is the former President of the New Zealand Open Source Society. He is currently working on Business Workflow Automation, and is the core maintainer for Gravity Workflow a GPL workflow engine.
I've developed a system that moves the business domain into the database, into metadata. This way the same physical infrastructure can service multiple services. This is far more efficient in terms of the number of servers as you don't need separate infrastructure for each service. This is not new, is a pattern used in SQL databases where schema isn't baked in, rather a runtime artifact. dev.to/cheetah100/micro-nightmares...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Article omits significant Saga pattern issue: every implementation is unique and tedious, can't be abstracted out to library/framework and, like Circuit Breaker, intermixed with business logic.
I've developed a system that moves the business domain into the database, into metadata. This way the same physical infrastructure can service multiple services. This is far more efficient in terms of the number of servers as you don't need separate infrastructure for each service. This is not new, is a pattern used in SQL databases where schema isn't baked in, rather a runtime artifact. dev.to/cheetah100/micro-nightmares...