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

Datomic Cloud support #17

Open
byronclark opened this issue Apr 30, 2023 · 1 comment
Open

Datomic Cloud support #17

byronclark opened this issue Apr 30, 2023 · 1 comment

Comments

@byronclark
Copy link
Contributor

It looks like there was some initial thought put into supporting Datomic Cloud (alias in deps.edn at least), but the current implementation is written to the Peer API and may need some work to support the Client API.

The initial issues I see are:

  • datomic.api.tx->t does not exist in the Client API
  • datomic.api.tx-range takes different args in Client API
  • datomic.Datom (used as a type hint) does not exist in the Client API

I'm happy to work on this as plenish looks like a great tool that would solve a lot of challenges for my team.

Would you be open to having support for Datomic Cloud in the project?

And since it looks like you started with Datomic Cloud, any major gotchas or challenges I should watch out for?

@plexus
Copy link
Member

plexus commented May 2, 2023

The fact that the alias is there doesn't indicate we're considering cloud support. It's most likely copied over from another project without much thinking.

We currently don't have clients that use datomic cloud, and so we have limited appetite for dealing with the additional complexity that supporting both apis brings with it. That might change if there is commercial interest.

Organizations that want to use plenish with datomic cloud should reach out to Gaiwan.co. ideally we find multiple interested parties so they can share the development cost.

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

No branches or pull requests

2 participants