Till new advice, I'm holding over this practice, It's just taking me too longer and I dont feel inspired now for microservices, JUST FOR NOW.

Maybe I'll do a more decent practice in the future. You can do pull requests if you like to this project if you feel you want to practice with a premade project.

Microservice introduction practice

Hi, welcome to my repo. I'm planning to get into Microservices, the design, programming and deployment of these services, as the design patterns too, security and more stuff.

It's gonna be ruff :c

DIAGRAMS BELOW CAN BE CHANGED OVER THE TIME I'M INVESTING IN THIS REPO

This is the initial schema, for now I'll be designing with diagrams the architecture of this stuff, hands off first, the general architecture of the small system I'm tryna make

Now I have to define the database schemas and the orchestor events with the saga pattern.

For stablishing solid procceses about what I want to do, I'm using use cases so I can set the processes that later I'll code, so I dont loose time thinking about what processes to do while already coding.

RELATIONAL DATABASES

I decided to try another relational to host user credentials instead of MongoDB as I specified in the arquitecture diagram

NoSQL DATABASES

It's just one :=P

DOCKER? I think for this practice no

This practice is taking longer than expected, because of two reasons: I'm lazy as fuck and I feel it's taking longer than expected. I wanted to use docker but the thing is that I want to reserve that topic for later.

While reading about microservices stuff with spring boot, I learned about a way to implement api gateways, by using Eureka from Netflix, far easier to use than docker.

All microservices hosted, of course I can access them but in theory, if I restrict the access to each microservice from the firewall and I just assign a DNS to the API Gateway, the clients can just interact with all microservices just from the gateway.