Skip to content
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

Merged
merged 3 commits into from
Apr 21, 2024

Conversation

dearrudam
Copy link
Contributor

@dearrudam dearrudam commented Apr 9, 2024

Ref: #3536

It is following the recommendation from @GraceJansen - #3650 (comment) - and @lauracowen - #3650 (comment) - ! (Thanks for the support!)

Changes:

  • Split the original blog post into 3 parts:
    • "Simplifying NoSQL Database Integration with Jakarta NoSQL"
    • "Jakarta NoSQL in Action: JNopo Game"
    • "Jakarta NoSQL in Action: Switching NoSQL Databases with Ease"

@dearrudam
Copy link
Contributor Author

@fabio-franco , could you review it for me ?!

@fabio-franco
Copy link
Contributor

Hi @dearrudam, sure! Sorry for the delay to reply. I have seen that for the draft it is not recommended to have the blog_tags.json, just for the next stage, the staging (https://github.com/OpenLiberty/blogs/tree/draft?tab=readme-ov-file). Is that ok for you to remove the blog_tags.json of this pr?

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.
Copy link
Contributor

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


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.
Copy link
Contributor

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

Signed-off-by: Maximillian Arruda <[email protected]>
Signed-off-by: Maximillian Arruda <[email protected]>
Signed-off-by: Maximillian Arruda <[email protected]>
@dearrudam
Copy link
Contributor Author

@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!?

@fabio-franco fabio-franco merged commit e0b74f7 into OpenLiberty:draft Apr 21, 2024
@fabio-franco
Copy link
Contributor

Here is the link to review it in the draft area: https://blogs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/blog/

@dearrudam
Copy link
Contributor Author

@fabio-franco, I need to update the API to the latest version... I'll open a new PR with this upgrade!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants