Summary

In this chapter, I started by explaining what modularity means and what bounded context, tightly coupled, generic, and plugin modules are. We've learned how to create a new module using the ABP CLI.

We then explored the structure of the Payment module and understood how it is integrated into the EventHub solution. We've learned the steps of manually installing the Payment module to the EventHub solution by setting up the project dependencies.

Finally, we've seen two approaches to using the payment database tables. The single database approach is simple and shares the same database between the EventHub application and the Payment module. On the other hand, the separate database approach allows us to use a dedicated database for the payment tables, making it possible to use a different DBMS for the Payment module than the main application.

I suggest checking the source code of the Payment module and the EventHub solutions to understand all the details...