Not finding what you need here? Ask on the forum.
When will Datomic Cloud be available anywhere other than AWS?
Datomic Cloud is built with many individual AWS services and relies on specific semantic and operational characteristics of these services. It is unlikely that an infrastructure-agnostic version of Datomic Cloud will be developed. If you have a requirement to run somewhere other than AWS, Datomic On-Prem can be deployed anywhere.
Is there an "offline" option for testing & development?
Datomic is a Cloud database, intended for use by and with applications that are cloud-resident. One presumption of a Cloud-specific architecture is availability of an internet connection. However, we are interested in feedback on needs and use cases and are considering additional tooling to improve the overall developer experience.
When will Datomic Cloud be available in additional AWS regions?
Datomic requires a suite of AWS services, some of which are only available in certain regions. We are actively working to support as many AWS regions as possible, and if you have a system or project that you would like to run in a currently unsupported region, please let us know!
What is the size limit of a Datomic Cloud database?
There is no hard limit on the size of an individual Datomic database. However, there are a number of operational considerations involved with running databases with a total history of more than 10 billion datoms. If your use case is likely to require more than 10 billion datoms, we would encourage you to contact us to discuss your system.
How many databases can I have in a single Datomic Cloud system?
While there is no specific limit on the number of logical databases supported by a single Datomic Cloud system, each database requires some amount of memory and computational overhead on all instances in the primary compute group. A Datomic Cloud system should contain the database(s) for a specific purpose, and you should create separate systems for databases that serve separate purposes. The system planning documentation provides additional details to aid in overall system design and configuration.
When should I increase the number of instances in the primary compute group?
You should NOT enable AWS Auto Scaling on the primary compute group. However, if you frequently write heavily to a larger number of databases than the number of instances in the compute group, you may wish to manually increase the overall size of the compute group to be equal to or slightly larger than the number of databases with significant write load.
Can we choose the backend storage?
Datomic utilizes a stratified storage stack to provide its semantic and operational guarantees. The stack includes redundant storage across S3, DynamoDB, EFS, local disk, and memory and has been designed to optimize reliability and performance.
Can we control the data storage region?
Datomic Cloud runs entirely within your AWS account in a single AWS region. Datomic will only use AWS resources in the region in which you create your system.
Can I temporarily "turn down" my system when it is not in use?
Yes, you can turn down your Auto Scaling Group to shut down any compute or query group without deleting any resources.
Do Ions support integration with other AWS services?
Ions are functions that run in the same JVM as your Datomic Cloud system. They can contain arbitrary Clojure code, including using external AWS services. You will need to configure your Ions using AWS IAM policies to grant them the AWS permissions necessary for their specific uses of other AWS services.