Refactoring the bookstore for ConductR

With a basic knowledge of ConductR under our belts, it's time to start making changes to the bookstore app to allow it to run in ConductR. We will also use the features of ConductR, namely service location, to complete the full separation of our services. When done, we will have a more loosely coupled set of services representing our bookstore app versus the monolith we were using up until this point. The next sections will break down each of the major things we need to do to get the bookstore app running within ConductR.

Splitting apart the bookstore projects

Coming into this chapter, we allowed the different application modules to have dependencies on each other. We saw this in how the sales-order-processing module had dependencies on inventory-management, user-management, and credit-processing. By having dependencies on these other modules, the sales-order-handling code can make direct actor calls to actors within those modules using messages classes...