MorphiaOrg / MorphiaOrg/morphia

Use MongoDB Reactive Streams internally to provide a sync and an async API

Open
#1,340 4 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement proposed
Dominant language
Java
Stars
1.7k
Forks
449
Avg merge
7m
Merged PRs (30d)
10

Description

Is your feature request related to a problem? Please describe.
I really want to use Morphia because of the clean API that the default MongoDB Java Driver does not provide. There is the "new" "POJO" feature, but you can't for instance update POJOs without writing manual queries. But Morphia does not support the "new" MongoDB Reactive Streams Java Driver, which can be used both for non-blocking and blocking requests.

Describe the solution you'd like
It would be great if the MongoDB Reactive Streams Java Driver could be implemented internally. Afterwards, an asynchronous Morphia API could be added in addition to the synchronous one. This could be realized by just using different Subscribers.

Describe alternatives you've considered
One alternative would be to use Morphia and deal with Threads by oneself but as I saw in other issues (#1289 and #829) I think I'm not the only one who would like an approach like this.

Additional context
None

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing Morphia's existing synchronous API and the MongoDB Reactive Streams Java Driver, including the related issues #1289 and #829. Done would require an internal reactive implementation plus both synchronous and asynchronous Morphia APIs, but this issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, mongodb
Domain
backend-api-design, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.