Is this a suitable architecture for a web application?
I've been trying to get my head around Domain-driven design architecture, and applying it to my application. I've started by focusing on a single entity (A "Shipping Group"), and a web API exposes simple CRUD operations. Here's the directory structure I've gone for:
Here's what I'm thinking:
domainholds the interfaces and models for the business logic and repository classes. The*Entitymodels are the data models used by repos, theModelmodels are used by the business logic layer.dynamodbis an implementation of the data layer (using the models and interfaces from the Domain directory) for Amazon's DynamoDBlambdais the web application layer, which happens to be written for AWS Lambda. It contains the relevant models and handlers, and calls down to the logic layer using the models and interfaces from thedomaindirectory.logicis the implementation of the business logic layer (using the models and interfaces from thedomaindirectory)
My questions are:
Is this a sensible structure?
Have I used terminology (e.g. the name of the
domaindirectory) appropriately?Similarly, do my naming conventions (especially with models) make sense?
ddd
asked 6 mins ago
devrobf
1641
add a comment |
I've been trying to get my head around Domain-driven design architecture, and applying it to my application. I've started by focusing on a single entity (A "Shipping Group"), and a web API exposes simple CRUD operations. Here's the directory structure I've gone for:
Here's what I'm thinking:
domainholds the interfaces and models for the business logic and repository classes. The*Entitymodels are the data models used by repos, theModelmodels are used by the business logic layer.dynamodbis an implementation of the data layer (using the models and interfaces from the Domain directory) for Amazon's DynamoDBlambdais the web application layer, which happens to be written for AWS Lambda. It contains the relevant models and handlers, and calls down to the logic layer using the models and interfaces from thedomaindirectory.logicis the implementation of the business logic layer (using the models and interfaces from thedomaindirectory)
My questions are:
Is this a sensible structure?
Have I used terminology (e.g. the name of the
domaindirectory) appropriately?Similarly, do my naming conventions (especially with models) make sense?
ddd
asked 6 mins ago
devrobf
1641
Code Review required real code. Skeletons of code are off-topic.
– 200_success
4 mins ago
add a comment |
I've been trying to get my head around Domain-driven design architecture, and applying it to my application. I've started by focusing on a single entity (A "Shipping Group"), and a web API exposes simple CRUD operations. Here's the directory structure I've gone for:
Here's what I'm thinking:
domainholds the interfaces and models for the business logic and repository classes. The*Entitymodels are the data models used by repos, theModelmodels are used by the business logic layer.dynamodbis an implementation of the data layer (using the models and interfaces from the Domain directory) for Amazon's DynamoDBlambdais the web application layer, which happens to be written for AWS Lambda. It contains the relevant models and handlers, and calls down to the logic layer using the models and interfaces from thedomaindirectory.logicis the implementation of the business logic layer (using the models and interfaces from thedomaindirectory)
My questions are:
Is this a sensible structure?
Have I used terminology (e.g. the name of the
domaindirectory) appropriately?Similarly, do my naming conventions (especially with models) make sense?
ddd
asked 6 mins ago
devrobf
1641
I've been trying to get my head around Domain-driven design architecture, and applying it to my application. I've started by focusing on a single entity (A "Shipping Group"), and a web API exposes simple CRUD operations. Here's the directory structure I've gone for:
Here's what I'm thinking:
domainholds the interfaces and models for the business logic and repository classes. The*Entitymodels are the data models used by repos, theModelmodels are used by the business logic layer.dynamodbis an implementation of the data layer (using the models and interfaces from the Domain directory) for Amazon's DynamoDBlambdais the web application layer, which happens to be written for AWS Lambda. It contains the relevant models and handlers, and calls down to the logic layer using the models and interfaces from thedomaindirectory.logicis the implementation of the business logic layer (using the models and interfaces from thedomaindirectory)
My questions are:
Is this a sensible structure?
Have I used terminology (e.g. the name of the
domaindirectory) appropriately?Similarly, do my naming conventions (especially with models) make sense?
ddd
ddd
asked 6 mins ago
devrobf
1641
asked 6 mins ago
devrobf
1641
asked 6 mins ago
devrobf
1641
asked 6 mins ago
devrobf
1641
asked 6 mins ago
devrobf
1641
1641
Code Review required real code. Skeletons of code are off-topic.
– 200_success
4 mins ago
add a comment |
Code Review required real code. Skeletons of code are off-topic.
– 200_success
4 mins ago
Code Review required real code. Skeletons of code are off-topic.
– 200_success
4 mins ago
Code Review required real code. Skeletons of code are off-topic.
– 200_success
4 mins ago
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
});
});
}, "mathjax-editing");
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: "196"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fcodereview.stackexchange.com%2fquestions%2f210148%2fis-this-a-suitable-architecture-for-a-web-application%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Code Review Stack Exchange!
- 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.
Use MathJax to format equations. MathJax reference.
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%2fcodereview.stackexchange.com%2fquestions%2f210148%2fis-this-a-suitable-architecture-for-a-web-application%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
Code Review required real code. Skeletons of code are off-topic.
– 200_success
4 mins ago