DDD project with AngularJs (SPA) web interface...is it a good idea?

Question

i am starting to implement an enterprise app using DDD guidelines. First of all, me and my team are starting our journey through DDD, so we have lot of things to learn and to understand (so forgive me if i say something...stupid=>)

The app will be a (very customized) CMS. The project will have:

• Domain and Backend developed using Microsoft stack (C#, WebAPI, EF6)
• Front-End developed as SPA using AngularJs

My biggest doubts are related to how (and how much) it will be possible to use the domain in a rich client application...i mean, if all the logic resides in the domain objects (back-end side), how should the communication between FE and BE be developed? Should the system do a sort of ping pong game for every changes done on the entities on FE side?

Or should i take some compromise? Anybody had a previous similar experience?

Answer 1

You probably want to generate the front-end from the domain. Generate client-side validations and calculations from your domain-side descriptions. Once it works, you can make your generator smart in that it starts using information about the amount of ping-pong needed (and even actual delay and throughput) to do caching