-
Notifications
You must be signed in to change notification settings - Fork 4
Home
The domain is the "Bed and Breakfast Booking". The company BedBreBo has a web portal bedbrebo.com that allows users to book a B&B room available in the BedBreBo catalog. User can select geographical region, reservation date and check availabilities of rooms. Once the choice is made he can book the room. bedbrebo.com allows business customers to subscribe and manage their B&B offers. Each business customer can add to the portal as many B&B offers as they want. They can update the schedule, number of available rooms, and see what has been already booked.
CQRS although simple in its definition is by no means a pattern that is very well understood. Most business applications out there in the wild do either not implement it at all or only partially follow its tenets. A lot of people also automatically associate CQRS with domain driven design (DDD) or event sourcing (ES) and other architectural patterns. But that is wrong. CQRS does not imply any of these other patterns. Yes, it’s true, CQRS can be used together with those patterns in a very straight forward way but it is not necessary.
This project is developed in a lunch time by a bunch of friends that whant to learn more about the architecture, DDD, CQRS and other patterns. We try to meet at least once a week. Some of us are also working on their free time after work. But the whole analysis, discussions and decisions are taken during the lunch time. Every time we meet, we try to record everything what we were talking about like for example what kind of design choices we have made, what decisions were taken. This help us out to track all the decisions. You can read it in the Log book section