VueJS
|
-------------
| |
postgre ----- Keycloak Kong ----- postgre
(+adminer) (+adminer)
|
------------------------------------------
| | | |
nodeJS mock go1 <-gRPC-> go2
- Kong/Keycloak Tutorial: a tutorial with a complete backend stack Kong/Konga/Keycloak/postgre_x2/mockbin
- vue-keycloak plugin: based on keycloack§js adapter, with examples
- keycloak containers examples: official repositoryfor Keycloak containers
- Kong integrations samples: Kong with multiple integrations (keycloak, elk, InfluxDB)
Service | Dependencies |
---|---|
VueJS |
|
Keycloak |
|
Kong |
|
µservices |
|
This should give the big picture (maybe think adding nginx to "mock" VPC entry point)
Then other µservices are supposed to be added grouped by projects into submodules (they should work independently of all of this)
- Projects bootstraping
- Day-to-day Development
- Testing (e2e) and QA environments setup
- Production recovery/re-install
docker compose up # details to init in start.sh
cd apps/vuejs-demo
npm run serve
- Keycloack admin: http://localhost:8180/admin/master/console
- Konga: http://localhost:1337/#!/plugins
- Kong API Gateway: http://localhost:8000
- Kong Admin API: http://localhost:8001
- VueJS: http://localhost:8080
- Project init made simple:
git clone && docker compose up && curl http://localhost:8080
- Project update made simple:
-
git pull && migrate
-
git pull && restore
-
- Submodules as solutions containing multiple µservices
- Demo gRPC with 2 go services
- Doc to add another service
- Update made simple (project/submodule level):
- migrate
- restore
- Structure by solutions (Gateway, solution1(go1, go2), solution2(submodule))