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

Eclipsestore Support #25310

Closed
1 task done
hu-chia opened this issue Feb 23, 2024 · 2 comments
Closed
1 task done

Eclipsestore Support #25310

hu-chia opened this issue Feb 23, 2024 · 2 comments
Labels
area: feature request 💡 resolution: should go to blueprint The solution will no be implemented in core, but rather be a blueprint
Milestone

Comments

@hu-chia
Copy link

hu-chia commented Feb 23, 2024

Overview of the issue

Support to use Eclipsestore to be persistence layer.

Eclipsestore is an interesting idea to replace databases, in my opinion, It is very suitable as the persistence layer of DDD.

Motivation for or Use Case

I love the JDL, but unfortunately, It is designed to design a SQL model, and SQL is too heavy in many areas, I found that jhipster supports MongoDB, why not eclipsestore?

Related issues or PR

there is no related issues or PR.

  • Checking this box is mandatory (this is just to show you read everything)
@atomfrede
Copy link
Member

Mostly eclipstore is quite new and imho serves a quite different purpose than the databases we support. It would be best to start this as a blueprint as the maintenance burden is quite huge and the core team can not handle it.

@hu-chia
Copy link
Author

hu-chia commented Feb 23, 2024

I'm trying to write a blueprint( overriding generator-jhipster-jooq ) to support eclipsestore, please do not close this issue, so that I can post the problems I'm having here.

@mshima mshima added area: feature request 💡 resolution: should go to blueprint The solution will no be implemented in core, but rather be a blueprint and removed area: triage theme: undefined labels Feb 23, 2024
@hu-chia hu-chia closed this as completed Feb 29, 2024
@deepu105 deepu105 added this to the 8.2.0 milestone Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: feature request 💡 resolution: should go to blueprint The solution will no be implemented in core, but rather be a blueprint
Projects
None yet
Development

No branches or pull requests

4 participants