#818 Refactor the MBS API to not write to the database
Opened 6 years ago by mprahl. Modified 6 years ago

As discussed in the blue team meeting, it'd be nice to have the MBS API not have write access to the database but instead just publish messages to the backend, which the backend can then process. This would help eliminate race conditions such as a user trying to cancel a build in the middle of a handler running. It also helps eliminate database caching issues (where the frontend changes the database but the backend still has the old data in its cache), this is currently mostly resolved by forcing database refreshes, but that would no longer be required. We would also need to change the module submission so it queries the database until the backend has processed the module submission and then return the module ID.


Login to comment on this ticket.

Metadata