Hi guys, in this lesson we will talk about crew service architecture and overview. core service will be similar with previous services like user service or service will provide us course crude operations in this micro service. Firstly, we will use super input with sipping bird, we will implement model view controller structures, our MVC structure will work like that. First of all, the end of the Colossus will be created under model package. Later, if model class is permanent, we will create the poster for it. Call repository from services.

Finally, call services from controllers. data will be presented to the client as API call. So separate graph controller will be used to handle it. In code service, we will use my skin as database. We will map our database tables to objects with hibernate. So we will provide object relational mapping with hibernate.

For database migration, we will use leaky bass. In leaky bass, we will define our database chains and spring will handle it on initialization. To clear code, we will use Bloomberg library to handle all dependencies of our service we all use Gradle. To sum up, in core service, we will implement similar things like previous services, but in our service, we will see a different important thing from other services. core service will be a consumer In service, we will consume other services to do it. We will use open, inclined feature of sibling clock.

Okay, that's all about cursor structure. Thank you.