Should website & API have a different hostnames? -

I'm making the webpad is of medium size, and it is created with a single page static JS + HTML app (backbone) , And is used by NGN) which reaches an API, which is hosted on the appropriate webserver.

Is the API under a different hostname, or the same hostname but different path? What could be possible & amp; Think of these options? Both options are possible thanks to NGN.

I would recommend using an intuitive, different environment. Access points such as example.com and api.example.com allow hostname to describe the purpose of each environment. It keeps different things and when using the same hostname for each it becomes obvious that what kind of request is being made in confusion. It is possible to use

example.com/api , but leadership can lead to future issues, where the directory is also used for other things. For example, is there a directory like example.com/newfeature in the example.com/newfeature/api ?

Finally, all this is a matter of personal priority though. Choose something that works in a clear way for your environment.