EDA & Vertical Slice Architecture
We've talked about the MServer pipeline and how this will integrate with the RServer nodes, to help manage the MOOVPAD apps at every level. This includes within the containers, and these within the VMs running on remote servers, and across the MOOVPAD system overall. In that view of the system, we're talking about system events (e.g. errors).
However there's also a consideration of the general operation of MOOVPAD apps and their integration with the webAPIs and each other. So for example, when a user chooses to save a change they've made to their MOOV program, this change needs to be updated (and perhaps shared) in multiple webAPIs and then propagated accordingly. And for this, MOOVPAD apps will employ event driven architecture approaches. This works well with the vertical slice architecture pattern used to build the webAPIs, and is more about information flow.
I've been aware of things like event buses through cloud services for a while now obviously. But its only recently that I've considered what a custom approach might look like if I were to put something together myself, specifically tailored to the needs of MOOVPAD apps, and how I could then integrate this with the management systems and modules to the left.
Brain go brrrrrrr 🙂
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.