You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I've been studying the Maestro source code.
I noticed that the open-source version of Maestro is designed for single-instance deployment. Although it has multiple modules like maestro-engine, maestro-server, and maestro-flow, only the maestro-server module actually runs as a service, with other modules being dependencies of maestro-server.
I also noticed that internal state transitions and asynchronous event processing are implemented using BlockingQueue. Does this approach risk data loss in case of system crashes?
I'd appreciate your feedback on whether my understanding is correct.
The text was updated successfully, but these errors were encountered:
gluttonweb
changed the title
关于Maestro开源版本的两个问题,期待您的解答
Two questions about the open-source version of Maestro, looking forward to your answers:(关于Maestro开源版本的两个问题,期待您的解答)
Feb 12, 2025
Hello, I've been studying the Maestro source code.
I noticed that the open-source version of Maestro is designed for single-instance deployment. Although it has multiple modules like maestro-engine, maestro-server, and maestro-flow, only the maestro-server module actually runs as a service, with other modules being dependencies of maestro-server.
I also noticed that internal state transitions and asynchronous event processing are implemented using BlockingQueue. Does this approach risk data loss in case of system crashes?
I'd appreciate your feedback on whether my understanding is correct.
—————————————————————————————————————————————————————————————————
你好,我研究了maestro源码,
不知道我这个理解是否正确,期待您的回复
The text was updated successfully, but these errors were encountered: