I'm writing to initiate a discussion about our Job Service's current architecture and its implications on the simplified architecture approach.
Context Setting The simplified architecture we're striving for focuses on centralizing database write operations. This design ensures data consistency by having a single point for write operations. In contrast, data actions and queries are handled by distributed components, primarily focused on reading data. The Problem Our current architecture in the Job Service deviates from this ideal. It relies heavily on a fully distributed implementation, using runtime to invoke remote REST calls. This approach is not in alignment with our objective of a simplified architecture, where writes should be centralized. The Point To realign with the simplified architecture goals, the Job Service needs a restructure similar to what has been implemented in Data Index. This change would involve co-locating the write operations with the runtime application. The execution of jobs would then be managed by a separate component, maintaining the integrity of the simplified architecture. I'm keen to hear your thoughts on this topic, any potential challenges you foresee, and suggestions for implementation. Looking forward to a fruitful discussion. - Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
