ContosoUniversityDotNetCore

What he probably means ( he doesn't go into details), is that you can create a simple monolith without splitting up everything. Which is basically true. But as soon as you go more complex, you'll probably wish you'd used DDD from the start. DDD is gaining traction, not because it's good. But because it's compatible with microservices. As an aside, i also like how jgobard developped ContosoUniversity ( https://github.com/jbogard/ContosoUniversityDotNetCore / https://github.com/jbogard/ContosoUniversity/tree/master/src... ) with vertical slices and feature folders.

Not sure I really mentioned much 'enterprise-level', beyond SQL Server? I guess I'm making it sound more complicated than it really is then, because this approach is actually a lot simpler than the 'N-tier' abstraction-hell of yesteryear. Jimmy Bogard has a simple example here: https://github.com/jbogard/ContosoUniversityDotNetCore Some code can probably explain it better than me ;)

> My proposal is to switch to json objects for information exchange between server and client. We'll get the benefits similar to SPA without rewriting for it If I understand your approach correctly, I often do something similar, but with modern ASP.NET Core MVC apps. Basically, I have a tiny bit of JavaScript that 'intercepts' all form POSTs and submits them using AJAX instead. Another tiny bit of JavaScript can then process the result and do something (update a table, display a message, redirect, whatever). I feel like this gives me the best of both worlds - the backend is very testable, and really straightforward for new developers to come up to speed on, while at the same time we remove a lot of full-page renders. You can find an example of this technique here[0] [0] https://github.com/jbogard/ContosoUniversityDotNetCore