PBCs(Packaged Business Capabilities) for Composable Enterprise Implementation

Overview

PBC is a concept that packages specific business functions as independent modules and provides them, similar to a business function that can be assembled like a block.

MSAEZ adds a PBC marketplace to the domain-centered design modeling (event storming, Eventstorming) to make microservices more effectively composed and business logic more flexible. The selected PBC in the analysis/design phase is already provided in a completed state with completed business logic and UI implementation, allowing developers to build services by combining ready-to-use functional modules without additional coding.

This allows complex features such as notification systems, user review management, and payment processing to be implemented quickly and efficiently in a proven manner, achieving both improved development quality and operational efficiency.

How to Perform

We will explain how to apply a complex payment processing feature using the Payment PBC Application Example. Specifically, we will detail the analysis/design and implementation methods for the case where the vehicle call service allows users to pay for completed rides based on the fare.

Analysis/Design



1. Drag&Drop the PBC from the left palette of the event storming model canvas to select and apply the desired function from the existing PBC list provided by MSAEZ.
(Since the payment system is needed, apply payment-system from the marketplace)




2. When the PBC draft named PaymentSystem appears at the bottom of the dispatch boundedContext, double-click the empty PBC model to open it.




3. In the PBC panel, you can select the ReadModel, Command, Event stickers related to the functions implemented in the PBC model, and select the stickers related to the functions used in the corresponding service.




4. Closing the PBC panel window shows that only the selected stickers are brought in, and the PBC model for PaymentSystem is completed as shown in the above image.




5. Then, connect the relation to make communication possible between the existing microservices and the PBC, and update the payment status and payment ID information in the ride information after the payment is completed, and make it possible to view the receipt later.




• Model showing payment system PBC applied to vehicle call service

Implementation


1. When the code viewer is opened, a folder named PaymentSystem is created, and when you follow the instructions in the ReadMe file, the implementation level is also created.




2. In the implemented UI, when you click the payment button at the bottom left, the payment detailed page opens, and when you click payment again, the payment UI provided by the PG company appears.




3. When the payment is completed, the paymentId and paymentStatus are registered, and when the receipt check button is created, when you click the receipt check button and enter the paymentId in the receipt check input, you can check the payment information.

uEngine has registered trademarks and uses trademarks. and MSA-Ez is licensed under the GNU General Public License version 3.0.