Umbraco v14 - 3 tier architecture possibilities

[DeanRITS]

Hi,

Not sure if this is the best place to ask this but I could not get a response on the official forum. https://our.umbraco.com/forum/using-umbraco-and-getting-started/115019-umbraco-v14-3-tier-architecture-possibilities

I understand variations of this question have been asked a lot in the past but with the substantial re-architecture that occurred for Umbraco v14 I was wondering what possibilities open up.

When you follow the tutorial setup, you get a very simple dev environment out of the box where you have the "website" and “backoffice” within one web project in VS, both are deployed on the same domain and port. The only real difference being that the backoffice is exposed via the /umbraco route. This site and back office seem to talk directly to a SQL Server database with no API layer in the middle.

With the release of Umbraco v14 the architecture diagram seems to suggest that there is an API layer that can sit between the web tier and database.

Does this imply we can move more toward a 3-tier architecture?: - Deploy the backoffice and “website” on different server and have the API ecosystem deployed between the database.

Something like the below:

Thanks,
Dean