Entity framework and Eager loading and enterprise application with DDD aproach
We are trying to create an ASP.NET MVC 4 application using entity framework with domain driven development style pattern approach. As you can see in our part of domain layer, we have a complex design. We need to load entity with lazy as well as eager methods. Unfortunately we have big problem with these methods in entity framework.
Entity framework and Eager loading and enterprise application with DDD aproach
We are trying to create an ASP.NET MVC 4 application using entity framework with domain driven development style pattern approach. As you can see in our part of domain layer, we have a complex design. We need to load entity with lazy as well as eager methods. Unfortunately we have big problem with these methods in entity framework.
Entity framework and Eager loading and enterprise application with DDD aproach
We are trying to create an ASP.NET MVC 4 application using entity framework with domain driven development style pattern approach. As you can see in our part of domain layer, we have a complex design. We need to load entity with lazy as well as eager methods. Unfortunately we have big problem with these methods in entity framework.
How to enrich a simple two endpoint SOAP application to become enterprise level?
Imagine you have some exchange of data between two endpoints (webservices or let’s call URL).
Data can travel in any way (Xml, Json, GET, POST) it doesn’t matter.
How to enrich a simple two endpoint SOAP application to become enterprise level?
Imagine you have some exchange of data between two endpoints (webservices or let’s call URL).
Data can travel in any way (Xml, Json, GET, POST) it doesn’t matter.
How to determine if a message should be a command message or event message?
Two enterprise integration patterns are the command message and the event message. I am working on a system in which we use messaging not only for integration with other systems, but for internal communication between services. It’s supposed to be an eventually consistent system, and services are supposed to be ignorant of each other (with exception to a couple special-purpose services). As such, we try to avoid things that feel like remote procedure calls (RPC or RPI). We have a bus and message-oriented middleware system, and all messages are broadcasted.
How to determine if a message should be a command message or event message?
Two enterprise integration patterns are the command message and the event message. I am working on a system in which we use messaging not only for integration with other systems, but for internal communication between services. It’s supposed to be an eventually consistent system, and services are supposed to be ignorant of each other (with exception to a couple special-purpose services). As such, we try to avoid things that feel like remote procedure calls (RPC or RPI). We have a bus and message-oriented middleware system, and all messages are broadcasted.
Does DDD make sense for apps which mostly present data?
I’m responsible for designing a dashboard and data manipulation front-end for a sale transaction database and am not quite sure what type of architecture to use. The database is populated by an external ETL system.
Does DDD make sense for apps which mostly present data?
I’m responsible for designing a dashboard and data manipulation front-end for a sale transaction database and am not quite sure what type of architecture to use. The database is populated by an external ETL system.
Does DDD make sense for apps which mostly present data?
I’m responsible for designing a dashboard and data manipulation front-end for a sale transaction database and am not quite sure what type of architecture to use. The database is populated by an external ETL system.