Book Image

Mastering ABP Framework

By : Halil İbrahim Kalkan
Book Image

Mastering ABP Framework

By: Halil İbrahim Kalkan

Overview of this book

ABP Framework is a complete infrastructure for creating modern web applications by following software development best practices and conventions. With ABP's high-level framework and ecosystem, you can implement the Don’t Repeat Yourself (DRY) principle and focus on your business code. Written by the creator of ABP Framework, this book will help you to gain a complete understanding of the framework and modern web application development techniques. With step-by-step explanations of essential concepts and practical examples, you'll understand the requirements of a modern web solution and how ABP Framework makes it enjoyable to develop your own solutions. You'll discover the common requirements of enterprise web application development and explore the infrastructure provided by ABP. Throughout the book, you’ll get to grips with software development best practices for building maintainable and modular web solutions. By the end of this book, you'll be able to create a complete web solution that is easy to develop, maintain, and test.
Table of Contents (24 chapters)
1
Part 1: Introduction
6
Part 2: Fundamentals of ABP Framework
11
Part 3: Implementing Domain–Driven Design
15
Part 4: User Interface and API Development
19
Part 5: Miscellaneous

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...