-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge the Jakarta NoSQL blogposts into draft #3695
Conversation
@fabio-franco , could you review it for me ?! |
Hi @dearrudam, sure! Sorry for the delay to reply. I have seen that for the draft it is not recommended to have the |
author_github: https://github.com/dearrudam | ||
seo-title: TITLE - OpenLiberty.io | ||
seo-description: | | ||
Nowadays, in the cloud era, switching between NoSQL solutions could be interesting to save resources and costs, but it could be a nightmare, specially if we're highly coupled to a particular vendor. It will cause some changes that will make this approach very expensive, like: time spent on the change, the learning curve of a new API to use with this database, the code that will be lost, the persistence layer that needs to be replaced, etc. This is where the flexibility of Jakarta NoSQL with an implementation like Eclipse JNoSQL together shines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: change specially
by especially
posts/2024-04-20-jakarta-nosql-challenge-switching-nosql-easily.adoc
Outdated
Show resolved
Hide resolved
|
||
Here's the challenge: let's suppose that it's needed to change the *JNopo*'s Document NoSQL database, *MongoDB*, to another Document NoSQL database for save money purposes, e.g. *Couchbase*. | ||
|
||
By using Jakarta NoSQL specification to connect to the NoSQL solutions, we got some benefits and one of them is that with just a few changes, we'll be able to archive this goal easily. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess achive
would fit better than archive
here
posts/2024-04-20-jakarta-nosql-challenge-switching-nosql-easily.adoc
Outdated
Show resolved
Hide resolved
posts/2024-04-15-simplifying-nosql-database-integration-with-jakarta-nosql.adoc
Outdated
Show resolved
Hide resolved
posts/2024-04-15-simplifying-nosql-database-integration-with-jakarta-nosql.adoc
Outdated
Show resolved
Hide resolved
Signed-off-by: Maximillian Arruda <[email protected]>
Signed-off-by: Maximillian Arruda <[email protected]>
Signed-off-by: Maximillian Arruda <[email protected]>
@fabio-franco, thanks for the feedback! I made the changes that you mentioned, could you review it again? @GraceJansen and @lauracowen, could you review it again!? |
Here is the link to review it in the draft area: https://blogs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/blog/ |
@fabio-franco, I need to update the API to the latest version... I'll open a new PR with this upgrade! |
Ref: #3536
It is following the recommendation from @GraceJansen - #3650 (comment) - and @lauracowen - #3650 (comment) - ! (Thanks for the support!)
Changes: