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.
Why are JOINS deprecated for a in-memory database?
Correct me if I’m misunderstanding. Refer to the following sentence:
Why are JOINS deprecated for a in-memory database?
Correct me if I’m misunderstanding. Refer to the following sentence:
A specific problem with architecturing a part of our application
Firstly, I’ll try to describe the real world model of what we are trying to express in C# code.
A specific problem with architecturing a part of our application
Firstly, I’ll try to describe the real world model of what we are trying to express in C# code.
A specific problem with architecturing a part of our application
Firstly, I’ll try to describe the real world model of what we are trying to express in C# code.
A specific problem with architecturing a part of our application
Firstly, I’ll try to describe the real world model of what we are trying to express in C# code.
DDD / Optimizing a specific service belonging to a specific bounded context regarding hardware
Well known is the split of a whole application into several bounded contexts to emerge an Ubiquitous language. while practicing Domain-Driven Design.
If I unite many web apps into one, will I save resources?
I’m comparing 2 different approaches of J2EE application architecture: