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

README is unclear about persistence limitations with CRuby #62

Open
rcrogers opened this issue Dec 8, 2014 · 0 comments
Open

README is unclear about persistence limitations with CRuby #62

rcrogers opened this issue Dec 8, 2014 · 0 comments

Comments

@rcrogers
Copy link

rcrogers commented Dec 8, 2014

https://github.com/relevance/diametric/blob/ae5fa808ae263c95eacb3ad896655e74d6f2a3b2/README.md

Diametric supports both CRuby and JRuby. When Diametric is used on CRuby, Diametric connects to Datomic's REST service. Using Datomic's REST API, Diametric creates schema/data and makes a queries to Datomic. When Diametric is used on JRuby, both Datomic's REST and Peer services are supported. The core parts of Peer service are implemented using Datomic API.
...
The biggest difference between REST and Peer services is available database types. REST service can use memory database only, which means we can't save data in any file as long as using free version. While Peer service can use memory and free version of transactor, which means we can save data in a file through Datomic's transactor.

I found multiple parts of this confusing:

  • "REST service can use memory database only" -- I can't find any documentation about this on the Datomic site. Are more details available?
  • "can't save data in any file as long as using free version" -- what if I want to use CRuby with Datomic Pro Starter? Can I persist data to disk in that scenario?
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

1 participant