In the way that it's described in that article and diagramed, the system doesn't look like microservices but like hybrid combination of services and microservices. Workflow engine has to many responsibilities to be microservice. In the nutshell it looks like typical event driven system with broker for running tasks. The microservices part is poorly described so there is no need to put emphasis on them.
Really enjoyed this. You can tell Netflix put a lot of thought into solving real pain points with Meson. Maestro sounds like a solid upgrade, especially with how it scales and supports different types of users, not just engineers. I like that it works with notebooks and has a visual interface too. That makes it way more approachable, the signal based triggering is a nice touch. I would love to hear more about how it actually performs at peak load in production and how teams are using it day to day
In the way that it's described in that article and diagramed, the system doesn't look like microservices but like hybrid combination of services and microservices. Workflow engine has to many responsibilities to be microservice. In the nutshell it looks like typical event driven system with broker for running tasks. The microservices part is poorly described so there is no need to put emphasis on them.
Also wonder if they had considered airflow and why they decided not to use it or improve it.
Thanks for sharing, great read
Great sharing!
Really enjoyed this. You can tell Netflix put a lot of thought into solving real pain points with Meson. Maestro sounds like a solid upgrade, especially with how it scales and supports different types of users, not just engineers. I like that it works with notebooks and has a visual interface too. That makes it way more approachable, the signal based triggering is a nice touch. I would love to hear more about how it actually performs at peak load in production and how teams are using it day to day