Same is true for any enhancements that are required to be made to a given module. ![]() What is even better is that the fixes once made need not be repeated in any other part of the application. Since the fixes are limited to modules, the impact analysis required and the regression issues introduced are drastically reduced, provided that the input and the output of the module is maintained. Maintenance: Any bugs and issues can be easily isolated and fixed within a module.Reusability: As these modules essentially follow a headless approach with well-defined interfaces, these can be used to cater to more than one feature in your application or even across applications.This design choice though very basic, brings in huge advantages, such as: These modules or even modules made of smaller modules can then be stitched together to create a neat loosely coupled application. ![]() One of the basic design choices here would be to identify the discrete functions that are required to build a feature and encapsulate the associated logic into smaller appropriately named granular modules, that have clearly defined interfaces for input and output. Thus, further adding to the maintenance costs, as any changes to one routine would have be repeated to a bouquet of other similar routines. Additionally, large portions of these monolithic applications must be duplicated in many parts of the application that share a similar function. ![]() The benefits of this choice however are often short-lived, as these monolithic applications are incredibly difficult to maintain and debug, owing to their sheer size and tight coupling. Writing large monolithic applications, enjoy general bias from the developers, as these can be tailored to fit the use cases and be coded faster. Please update any bookmarks or links that you may have to this location. This article has been moved over to our Pega Community here in order to align with our larger content strategy. 1 Application modularization, encapsulation, and naming for better reuse and maintenanceĪpplication modularization, encapsulation, and naming for better reuse and maintenance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |