Why We Said 'No' to Apache Airflow and Built Our Own Workflow Engine | HackerNoon
Briefly

Decision-making in selecting the right framework is crucial; a wrong choice early on could lead to significant obstacles later as requirements evolve and codes grow.
Existing workflow platforms fall short of our needs; they may lack critical functionalities like task force-kill options or suffer from reliability issues like tasks getting stuck.
Simplicity in design is key—like maintaining an old car versus a complex new model. Fewer components lead to greater reliability and easier understanding.
Understanding your requirements and the context is essential. As wise individuals put it, "Understanding a problem clearly is the first step to solving it."
Read at Hackernoon
[
|
]