Xsemble release 3.4 comes with parameterization enhancements that broaden the reusability from single component level to the entire project level.
Xsemble 3.3 brings code level enhancements to Xsemble projects. Generated code templates are aligned with static code analyzers (linters) and use primitive types.
Xsemble has inbuilt powerful mechanisms to create components that are independent of one another and their environment. This gives rise to high component reuse.
Xsemble 3 is a major release. It aims to shoot beyond the Java EE technology that it has been supporting from the beginning.
With prevalent technologies, achieving a good component isolation is challenging due to the implicit component coupling.
This article shows how to use the Process Flow Diagram (PFD) of the Enhanced Software Development process to track the project progress.
With help of a demo application, we understand how a microservices application is built with small Xsemble components.
Benefits of using microservices are amplified further in an Xsemble based application. Xsemble based microservices offer benefits such as ease of refactoring, scalability of development and code reuse.
Critical information needed to manage software development process is hidden deep inside the code, risking project failure. Enhancing the process with Xsemble resolves these challenges, leading to project success with confidence.