Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>as you have read the DDD book by Vaughn Vernon, so know that DDD is all about tackling the complexity by understanding the problem first and solving it in Domain model. it doesn't matter which technology or tools you are using (Note: it's recommended to use an object oriented language) to promote your application. we had the similar issue a few years ago (different BC inside one desktop application) and we used windows application for presenting. WPF is more flexible because of it's powerful binding feature witch let's you use MVVM patter and dependency injection.</p> <p>Is it OK to have several BC in the same windows application? as I mentioned bounded contexts of DDD could be presented in one windows or web Application because they have their own service and repository implementation. don't assume bounded contexts of DDD as separate project! BCs could be successfully used in other project's Domain and not a separate project. </p>
    singulars
    1. This table or related slice is empty.
    1. POCan different bounded context (BC) leave in one WPF application?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USEhsan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI think the original question is more about how one would integrate/work with the the different BCs from the UI. More specifically: How do you design the UI access to those BCs? Do you create an extra facade atop of the different BCs such that your UI is oblivious to the different BCs? Or do you call the BCs "directly", e.g., by sending BC-specific commands to a common event bus? In the first case, a lot of extra complexity/code duplication is needed that might be overkill. In the second case the UI is aware of the different BCs and is "tightly" coupled to them. Best practices?
      singulars
      1. PO
      1. USAlexander Langer
    2. COyou can design different UI for each bounded context or a UI for different bounded context, it's based on your application. you can use event but or use CQRS patter for a bounded context in a solution. I recommend you to take look at this practice https://github.com/elbandit/DVD-Rental
      singulars
      1. PO
      1. USEhsan
    3. COThanks for the hint at the DVD-Rental example. It uses one UI per BC (e.g., the Subscription BC for the customers, and the Fullfillment BC/Operational UI for the staff, both of which are used by different parties -- staff vs. clients). The original question asks what to do if a _single_ UI spans multiple BCs (e.g., "production monitoring" and "production qualitiy"). This is a natural demand because customers (including our own) naturally want to use _one_ application only, not twenty just because under the hood the architect decided to use twenty BCs.
      singulars
      1. PO
      1. USAlexander Langer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload