Return HTML from bounded context
I've recently read a book about Domain Driven Design. But, I surprised when I read that sending back the HTML from bounded context to the presentation layer is one of the two approaches to return data from bounded context(another is via various data types like JSON and XML, ... as everyone uses it)!
This is the exact content of the book:
HTML APIs versus Data APIs
By constructing web pages with snippets of HTML that are returned from
each bounded context, you give bounded contexts control of the
appearance and behavior of specific regions of a page.
Now, I have two question about this:
- Is it really a good way to return HTML?
- Where HTML should be generated? In the application services as the last layer of bounded context or other layers or what?
reference: PATTERNS, PRINCIPLES, AND PRACTICES OF DOMAIN-DRIVEN DESIGN
By Scott Millet & Nick Tune, published by Wrox
domain-driven-design bounded-contexts
add a comment |
I've recently read a book about Domain Driven Design. But, I surprised when I read that sending back the HTML from bounded context to the presentation layer is one of the two approaches to return data from bounded context(another is via various data types like JSON and XML, ... as everyone uses it)!
This is the exact content of the book:
HTML APIs versus Data APIs
By constructing web pages with snippets of HTML that are returned from
each bounded context, you give bounded contexts control of the
appearance and behavior of specific regions of a page.
Now, I have two question about this:
- Is it really a good way to return HTML?
- Where HTML should be generated? In the application services as the last layer of bounded context or other layers or what?
reference: PATTERNS, PRINCIPLES, AND PRACTICES OF DOMAIN-DRIVEN DESIGN
By Scott Millet & Nick Tune, published by Wrox
domain-driven-design bounded-contexts
add a comment |
I've recently read a book about Domain Driven Design. But, I surprised when I read that sending back the HTML from bounded context to the presentation layer is one of the two approaches to return data from bounded context(another is via various data types like JSON and XML, ... as everyone uses it)!
This is the exact content of the book:
HTML APIs versus Data APIs
By constructing web pages with snippets of HTML that are returned from
each bounded context, you give bounded contexts control of the
appearance and behavior of specific regions of a page.
Now, I have two question about this:
- Is it really a good way to return HTML?
- Where HTML should be generated? In the application services as the last layer of bounded context or other layers or what?
reference: PATTERNS, PRINCIPLES, AND PRACTICES OF DOMAIN-DRIVEN DESIGN
By Scott Millet & Nick Tune, published by Wrox
domain-driven-design bounded-contexts
I've recently read a book about Domain Driven Design. But, I surprised when I read that sending back the HTML from bounded context to the presentation layer is one of the two approaches to return data from bounded context(another is via various data types like JSON and XML, ... as everyone uses it)!
This is the exact content of the book:
HTML APIs versus Data APIs
By constructing web pages with snippets of HTML that are returned from
each bounded context, you give bounded contexts control of the
appearance and behavior of specific regions of a page.
Now, I have two question about this:
- Is it really a good way to return HTML?
- Where HTML should be generated? In the application services as the last layer of bounded context or other layers or what?
reference: PATTERNS, PRINCIPLES, AND PRACTICES OF DOMAIN-DRIVEN DESIGN
By Scott Millet & Nick Tune, published by Wrox
domain-driven-design bounded-contexts
domain-driven-design bounded-contexts
edited Nov 10 '18 at 8:40
asked Nov 10 '18 at 7:25
Siamak Ferdos
1,62611741
1,62611741
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I think the book is talking about composed UIs there. The html returned by each BC means the UI of the BC. The whole UI is a composition of all UIs. So each BC has its own UI.
Another approach would be to have just one UI. The BCs would have no UI, just application layer. The UI would call the application layer of the BC it needs, usually the glue between the UI and the BCs APIs would be a REST API gateway.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236878%2freturn-html-from-bounded-context%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think the book is talking about composed UIs there. The html returned by each BC means the UI of the BC. The whole UI is a composition of all UIs. So each BC has its own UI.
Another approach would be to have just one UI. The BCs would have no UI, just application layer. The UI would call the application layer of the BC it needs, usually the glue between the UI and the BCs APIs would be a REST API gateway.
add a comment |
I think the book is talking about composed UIs there. The html returned by each BC means the UI of the BC. The whole UI is a composition of all UIs. So each BC has its own UI.
Another approach would be to have just one UI. The BCs would have no UI, just application layer. The UI would call the application layer of the BC it needs, usually the glue between the UI and the BCs APIs would be a REST API gateway.
add a comment |
I think the book is talking about composed UIs there. The html returned by each BC means the UI of the BC. The whole UI is a composition of all UIs. So each BC has its own UI.
Another approach would be to have just one UI. The BCs would have no UI, just application layer. The UI would call the application layer of the BC it needs, usually the glue between the UI and the BCs APIs would be a REST API gateway.
I think the book is talking about composed UIs there. The html returned by each BC means the UI of the BC. The whole UI is a composition of all UIs. So each BC has its own UI.
Another approach would be to have just one UI. The BCs would have no UI, just application layer. The UI would call the application layer of the BC it needs, usually the glue between the UI and the BCs APIs would be a REST API gateway.
edited Nov 11 '18 at 20:07
answered Nov 11 '18 at 19:46
choquero70
1,17111531
1,17111531
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236878%2freturn-html-from-bounded-context%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown