Session
Saving Current State Considered Harmful
Understand why applications using traditional stateful database approaches in the cloud consistently go awry and cause problems that ripple through our systems and teams.
We've come to accept this pain and trouble as part of the price of doing business in building distributed systems, but we really don't need to.
Saving execution history instead of current state preserves the execution coordinate across services and time and leaves us always knowing the next step.
Chris Condron
Event Systems Expert, Founder EventHorizion.io
Boston, Massachusetts, United States
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top