Hello buddies,
I have a doubt about the micro services and the DDD.
Imagine I have like 5 micro services, each of them has its own repo and maybe its own docker container. The services communicate between them with api/queues or whatever.
And for the web interface I have something with ReactJS or Angular maybe, but I want to make an app for mobile or a desktop app later.
My question is, what is the best way to get the information? Make every micro service have a public URL and a public API? Or make 1 micro service whose only function is to communicate with the others and act as a "facade" or a entry point?
I think with a single entry point it's nicer because the URL is always gonna be the same and you can make other micro services more secure. But I don't know if anyone else does something similar.
sssss
Student, Geek, Open-Sourcerer
I have been working on a side-project called ShibaManga. It is supposed to be a fast, mobile-first, offline-first online manga reader. The backend was build with nodejs, cassandra db, elastic search and redis. The backend is comprised of http micro-services. These micro-services have their own repo and their own docker container. They are linked together with docker-compose. I have 1 container that is a JSON REST API with koa that validates the requests and speaks to the endpoint micro-services which call other services themselves.
Micro is this great http micro service framework that is really simple and fast to use.
Caddy is used as the static file server for all the html, css, js and other assets but also as a http2 TLS proxy for the API.
The front-end is build with React, Redux, and react-mdl. The front-end then just requests data from the REST api.
All the source code is available at Github (I warn you though, most of the backend code is really ugly at the moment as i am moving away from my initial monolithic app).