- As Gateway server monolith, I used the SOA architecture infrastructure because it didn't have much room to grow, so we can say that SOA is a layered architecture, but it does give us strength, if the project grows, not as much as a hexagonal and DDD-enhanced structure
Username: "randomSecureKeyUsername!", Password: "randomSecureKeyPassword!"
POST
{
"username":"Test_username",
"password":"Test_pasw",
"name":"Test_name"
}
POST
It return a jwt
{
"username":"Test_username",
"password":"Test_pasw",
"name":"Test_name"
}
or
{
"username":"Test_username",
"password":"Test_pasw"
}
POST
Require JWT
{
"userId":1,
"firstName":"Test_name",
"lastName":"Test_last_name",
"birthDate":"2014-04-29"
}
GET
Require JWT
GET
Require JWT
DELETE
Require JWT
POST
Require JWT
{
"userId":1,
"firstName":"Test_name",
"lastName":"Test_last_name",
"birthDate":"2014-04-29"
}
GET
Require JWT
GET
Require JWT
DELETE
Require JWT
- Open terminal
- Go to gateway-server directory with cd command
- Run command that
docker run build -t gateway-server-image .
- Go to driver-service directory with cd command
- Run command that
docker run build -t driver-service-image .
- Go to passenger-service directory with cd command
- Run command that
docker run build -t passenger-service-image .
- Go to notification-service directory with cd command
- Run command that
docker run build -t notification-service-image .
- Go to payment-service directory with cd command
- Run command that
docker run build -t payment-service-image .
- Go to gateway-server directory with cd command
- Run command that
docker-compose up
- Open terminal
- Go to gateway-server directory with cd command
- Run command that
docker-compose -f docker-compose_v2.yml up