API design – splitting into different sub-domains (micro-services)

Our application is based on an API first architecture and is currently based on a single domain / service:


  • Starting multiple services inside Docker container
  • Unable to see images built through docker remote api's in docker cli result
  • Obtaining a docker image's parent images
  • nginx docker-image not reachable
  • All external DNS queries fail from within docker container
  • How to set environment variable as docker image name on build
  • Consumers of the API are :

    • Our web-frontend
    • Our mobile-apps
    • Other business / public

    We will be building new micro-services written in different languages for the same application. For example we might develop API services for:

    • Statistics
    • Blog / Content
    • RSS Feed
    • Search

    My question is around dealing with domains. Would it be best to split each service into a different subdomain e.g.

    • api.todos.com
    • stats.todos.com
    • content.todos.com
    • rss.todos.com
    • search.todos.com

    Or is it better to have a single unified API domain where we do HTTP (layer 7) routing to reach our endpoints. e.g.

    • api.todos.com/todos
    • api.todos.com/stats
    • api.todos.com/content
    • api.todos.com/rss
    • api.todos.com/search

    Not sure which is preferable for a public API? It would be easier to have multiple sub-domains and not have to deal with an intermediate routing layer / proxy.

  • Unable to access Container url in Bluemix for Spring Boot Application
  • Gitlab always shows “No container image repositories in Container Registry for this project.”
  • Why won't my docker-entrypoint.sh execute?
  • .bash_profile does not work with docker php image
  • How can ichange a virtualbox configuration using docker-machine
  • Docker doesn't start MONGODB, and IPAddress doesn't appear, when started with other services
  • One Solution collect form web for “API design – splitting into different sub-domains (micro-services)”

    As System Architect I think it is better to have a single unified API domain where we do HTTP (layer 7) routing to reach our endpoints. You can make your system more flexible without any changes for your clients. For example you have a microservice with routes:

    • api.todos.com/route1
    • api.todos.com/route2

    In future you can split the microservice by this routes.

    But mostly, it depends on what API Gateway will you use. API gateway is single entry point in your system, what proxy request to correct microservice. Also it make auth and cache. More about this microservice’s pattern you can read here.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.