BEST PRACTICES FOR DESIGNING OOZIE WORKFLOWSInternet Database Management ServicesUpdated on Feb 9, 2016 View more like this | Visit LOS GATOS, CA | Contact Priyanka Jain |
When designing Oozie Workflows, try to follow best practices for code reuse. Based on these best practices, Workflows should be large enough to encapsulate complete business functionality. On the other hand, similar to any other software develop-ment, the larger the process is, the more difficult it is to debug and maintain it.
This means that Oozie Workflow design is a compromise between trying to keep a process as small as possible, and ensuring that it implements a complete business function. If the business functionality of the process is fairly large, one of the common process design practices is componentization, based on the use of sub-processes (sub-Workflows, in the case of Oozie).
This means that Oozie Workflow design is a compromise between trying to keep a process as small as possible, and ensuring that it implements a complete business function. If the business functionality of the process is fairly large, one of the common process design practices is componentization, based on the use of sub-processes (sub-Workflows, in the case of Oozie).
