Tip:
Highlight text to annotate it
X
Based on the use cases I previously defined. I broke the system into three areas that I
felt would service top level management. Everything downstream of the inventory service would
handle everything that has to do with managing vehicle inventory. This can be from regular
crud functionality used in maintaining the cars in the database to providing information
about car availability in the future. The service could also handle things like taking
cars off line for mechanical upkeep or putting older cars up for sale, etc. the rental service
will handle anything dealing with rentals or reservations. This includes not only the
ability to reserve and rent cars but also to cancel reservations and even remove dead
reservations from the system for cars that were reserved but were never picked up a rental.
The service could also provide a user with information on currently rented are currently
reserved cars as well as history of their past rentals. The account service will deal
with everything having to do with customer user accounts. This includes providing employees
with customer information or even allowing the customer themselves to manage the information
the only thing the service will not handle regarding accounts is to be registration and
login synthesis can be handled by the websites membership subsystem. All three services will
serve as the gatekeepers of the middle tier. The frontline of the API. This means that
everything behind them is can be extracted from all the clients. The services can either
axes. Data directly to one of the data repositories. They also learn about or if behavior reusability
becomes necessary in some cases a service can call upon a business engine, which would
house that behavior. All three of these services are to be fully testable and alternate take
advantage of dependency injection. That's can provide them with any additional classes
on which they may depend