I'm creating a website that uses microservice API's on the backend to support the frontend UI.

My question is whether there is a common practice on what URL naming convention to give the API's?

So let's say my public website that a customer can go to is www.example.com and there are 3 API's that support it:

  1. one to manage authentication
  2. one to manage the purchasing and checkout system
  3. and one to pass the site product information

Let's call each one the auth, checkout and product service respectively.

The way I was currently thinking was something like www.{service name}.example.com eg. www.auth.example.com.

What do people think? Yay or nay?

0 Answers