Is using a database wrapper microservice an anti-pattern?
Say I have a microservice that wraps a database, in a way that the entire functionality of that service is hiding the details of the database behind a generic (say REST) API, allowing changing the database without affecting the other services.
Is this an anti-pattern?
What are the pros/cons of this approach?
database microservices anti-patterns
asked Nov 12 at 16:44
omer
126111
add a comment |
Say I have a microservice that wraps a database, in a way that the entire functionality of that service is hiding the details of the database behind a generic (say REST) API, allowing changing the database without affecting the other services.
Is this an anti-pattern?
What are the pros/cons of this approach?
database microservices anti-patterns
asked Nov 12 at 16:44
omer
126111
1
This seems like a good pattern. It is called an API and is quite common.
– Hogan
Nov 12 at 16:46
On the other hand, it adds an additional hop in or become a bottleneck, which might have a performance impact, and a general guideline in microservices is that services should implement business logic and use database for persisting state. In this case, the database is the service itself.
– omer
Nov 12 at 16:47
If you are asking permission to not use an API wrapper because it is an "anti-pattern" I doubt you will get any agreement here. What you describe is a pattern not an anti-pattern.
– Hogan
Nov 12 at 18:01
add a comment |
Say I have a microservice that wraps a database, in a way that the entire functionality of that service is hiding the details of the database behind a generic (say REST) API, allowing changing the database without affecting the other services.
Is this an anti-pattern?
What are the pros/cons of this approach?
database microservices anti-patterns
asked Nov 12 at 16:44
omer
126111
Say I have a microservice that wraps a database, in a way that the entire functionality of that service is hiding the details of the database behind a generic (say REST) API, allowing changing the database without affecting the other services.
Is this an anti-pattern?
What are the pros/cons of this approach?
database microservices anti-patterns
database microservices anti-patterns
asked Nov 12 at 16:44
omer
126111
asked Nov 12 at 16:44
omer
126111
asked Nov 12 at 16:44
omer
126111
asked Nov 12 at 16:44
omer
126111
asked Nov 12 at 16:44
omer
126111
126111
1
This seems like a good pattern. It is called an API and is quite common.
– Hogan
Nov 12 at 16:46
On the other hand, it adds an additional hop in or become a bottleneck, which might have a performance impact, and a general guideline in microservices is that services should implement business logic and use database for persisting state. In this case, the database is the service itself.
– omer
Nov 12 at 16:47
If you are asking permission to not use an API wrapper because it is an "anti-pattern" I doubt you will get any agreement here. What you describe is a pattern not an anti-pattern.
– Hogan
Nov 12 at 18:01
add a comment |
1
This seems like a good pattern. It is called an API and is quite common.
– Hogan
Nov 12 at 16:46
On the other hand, it adds an additional hop in or become a bottleneck, which might have a performance impact, and a general guideline in microservices is that services should implement business logic and use database for persisting state. In this case, the database is the service itself.
– omer
Nov 12 at 16:47
If you are asking permission to not use an API wrapper because it is an "anti-pattern" I doubt you will get any agreement here. What you describe is a pattern not an anti-pattern.
– Hogan
Nov 12 at 18:01
1
1
This seems like a good pattern. It is called an API and is quite common.
– Hogan
Nov 12 at 16:46
This seems like a good pattern. It is called an API and is quite common.
– Hogan
Nov 12 at 16:46
On the other hand, it adds an additional hop in or become a bottleneck, which might have a performance impact, and a general guideline in microservices is that services should implement business logic and use database for persisting state. In this case, the database is the service itself.
– omer
Nov 12 at 16:47
On the other hand, it adds an additional hop in or become a bottleneck, which might have a performance impact, and a general guideline in microservices is that services should implement business logic and use database for persisting state. In this case, the database is the service itself.
– omer
Nov 12 at 16:47
If you are asking permission to not use an API wrapper because it is an "anti-pattern" I doubt you will get any agreement here. What you describe is a pattern not an anti-pattern.
– Hogan
Nov 12 at 18:01
If you are asking permission to not use an API wrapper because it is an "anti-pattern" I doubt you will get any agreement here. What you describe is a pattern not an anti-pattern.
– Hogan
Nov 12 at 18:01
add a comment |
active
oldest
votes
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%2f53266565%2fis-using-a-database-wrapper-microservice-an-anti-pattern%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 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%2f53266565%2fis-using-a-database-wrapper-microservice-an-anti-pattern%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
1
This seems like a good pattern. It is called an API and is quite common.
– Hogan
Nov 12 at 16:46
On the other hand, it adds an additional hop in or become a bottleneck, which might have a performance impact, and a general guideline in microservices is that services should implement business logic and use database for persisting state. In this case, the database is the service itself.
– omer
Nov 12 at 16:47
If you are asking permission to not use an API wrapper because it is an "anti-pattern" I doubt you will get any agreement here. What you describe is a pattern not an anti-pattern.
– Hogan
Nov 12 at 18:01