Hello everyone, I just created a small design document for Hotel Searching sites (e.g. like Trivago).
- Vacation Aggregator system is very popular internet-related services and products in the hotel solution.
- While designing this solution many challenges were encountered like segregating the services into microservices as per the business logic, design relationship between entity, identifying key attribute, operations to be performed by user, user hotel search and reservation.
- Following are the components identified in this solution
Actors :- User, Hotel service provider, Administrator
Benefits of Solution:- Reusable, extendable, maintainable
Design decisions /patterns Used
- Layered architecture is used to simplify the user interface.
- Service layer which provides Centralizes external access abstracts internal implementation.
- Business layer handles the business rules of each microservices services
- Data access layer simplified access of the database.
- Design pattern used
- Facade design pattern is used to help client applications to easily interact with the system and provide an interface to a set of interfaces in a subsystem
- Singleton design pattern ensures a class has only one instance and provides a global point of access to it.
- Adapter design pattern is used to convert the interface of a class into another interface the application expects.
- Microservices Orchestration Pattern that acts as the “orchestrator” of the overall service interaction.
Use Case
Component Diagram
Class Diagram
Sequence Diagram
ER Diagram
Let me know if you have a better suggestion. Thanks. ✌
