Unit Of Work Systems
Working with distributed databases and server modules, there is a greater chance for things to go wrong. That's why I'm grateful to have found some good examples and learning resources to help guide the design of the MOOVPAD server-side systems. Most recently, the focus has been on the concepts of unit of work and transaction patterns.
In essence, these basically mean that when there are multiple related database calls happening together, and they are all required to succeed in order for the system to function right overall, they are managed together until that success is assured at the end.
I don't do the learnings justice, but that's the general idea. And I say that like I actually have a clue lol 🙂
Stay awesome,
EMH
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.