Yes, this is a proven architecture. It is called client/server, or 3-tiers, and it's been around for decades. But you didn't write very much about your applica

Yes, this is a proven architecture. It is called client/server, or 3-tiers, and it's been around for decades. But you didn't write very much about your application's requirements, so it's not clear if this architecture is the best fit. In general I would recommend that for a website (content-based), it's better to stick with generating HTML on the server. For applications (heavy user interaction) I would recommend going for client/server, and generating the UI dynamically on the client. My reasoning is that for a website, generating the pages on the server leads to a simpler architecture, faster response times and easier SEO. And for applications, keeping state and UI client-side leads to increased responsiveness and easier scalability (since there is less state server-side and the requests are service-based).