Do I need to move the admin API to a separate application?

Question

Software design

Hello.
If you are developing a SPA with a user account and an admin panel, then as is more common, keep the API on the same domain and separate requests along the way (for example, everything that starts with / admin is requests from the admin panel), or the admin API should be made as a separate application on a separate domain with all the consequences?
The pros/cons, in principle, are clear, for example, if the admin panel/cabinet is distributed over different servers, then in the case of one application, you will also have to drag the code/dependencies for the user cabinet, which will not be needed there.

Answer 1

Well, let's start with which http endpoint the admin panel is located on and the main project does not affect almost anything, since this is only a matter of traffic routing. As for dependencies, each application has its own, although SDKs for working with microservices must be packaged and connected as and when needed.
In fact, these are two completely different SPAs.