My FeedDiscussionsHeadless CMS
New
Sign in
Log inSign up
Learn more about Hashnode Headless CMSHashnode Headless CMS
Collaborate seamlessly with Hashnode Headless CMS for Enterprise.
Upgrade ✨Learn more

What's the best implementation for Micro Services/API with back/front frameworks?

Sergio's photo
Sergio
·Oct 26, 2016

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.