How do compatible class libraries, MVVM, and DDD work?

So, we focus on developing an enterprise web application that uses DDD templates with CQRS + ES. We have a good pen at the enterprise level. Now that we want to open our backend services for native mobile devices using Xamarin and portable class libraries, how does this integrate? Have our domain projects changed in each of our limited contexts as a type of PCL project? What will we do with the MVVM side, for example, in the Windows Store application, Windows Phone application? Since we are leaving the web API service, are we going to a limited PCL context library or are we creating a subset model and a separate PCL library for our own MVVM client templates?

Now we are inclined to ensure that the original DDD projects are class libraries and simply create a separate portable class library for our MVVM code. We will probably use file binding to refer to domain projects in order to get models so that we always have the latest set of POCO objects and any DTO objects that we want to use on the client. Anyone have any thoughts or ideas on this? I really don't see much discussion around this combination of DDD + PCL.

+4
source share
1 answer

I thought a lot about this, and what I did to put Xamarin in my current architecture using the DDD approach was:

  • PCL , , Xamarin.Forms, Xamarin.Android, Xamarin.iOS, ASP.NET, WCF ..

  • , . Presentation, ASP.NET MVC.

  • Xamarin . ASP.NET Web Api WCF REST. DDD.

  • xamarin , . Xamarin . , . " " -.

, -, DDD .

+1

Source: https://habr.com/ru/post/1535965/


All Articles