Ions let you develop applications for the cloud by deploying your code to a running Datomic compute group. You can focus on your application logic, writing ordinary Clojure functions, and the ion tooling and infrastructure handles the deployment and execution details. You can leverage your code both inside Datomic transactions and queries, and from the world at large via built-in support for AWS Lambda and web services.
There are four activities involved in using Datomic Ions:
- dev - Write your application as a set of ordinary Clojure functions.
- push - Capture your current local view of the world as a revision you can later deploy.
- deploy a revision to a Datomic compute group.
- bond - Use the functions you have deployed in transactions, queries, AWS Lambdas, or web services.
- Focus on your application.
- Leverage your Datomic Cloud cluster compute resources and data locality.
- Extend Datomic transactions and queries with your own logic.
- Connect to the broader AWS cloud via Lambda events.
- Service web consumers with API Gateway.
- Scale Datomic and your app together.
- Deliver on AWS with high agility.
You devlop ions in an ordinary tools.deps based Clojure project kept in git. You can have git and maven dependencies, and even local deps of libs in progress.
Ions include one or more entry points. These are Clojure functions that have a signature matching their intended use:
- Transaction functions take and return transaction data.
- Query expressions take an return arbitrary data.
- Lambdas take and return JSON payloads. Ion Lambdas can handle AWS events, or you can invoke them directly.
- Web service functions support ring-like edn handlers.
You can develop and test these entry points (and all their supporting code) as ordinary Clojure functions at the REPL.
You capture the current state of your application code by invoking push. push creates a named CodeDeploy revision in Amazon S3, which you can later deploy to one or more Datomic compute groups. If you are working on committed code with no local deps you will get a repropducible revision named after your commit. For work in progress, you will have to supply a name for your (unreproducible) revision.
push reads your deps.edn and ensures all library dependencies and local code are moved to S3. In addition, it creates a first-class revision in Code Deploy. push is smart about minimizing the transfer of code to S3.
When you create a primary compute group or query group, you associate
it with a Code Deploy application. The
:app-name in your
ion-config.edn connects your code to a Code Deploy application and
determines which compute groups you can deploy to.
deploy uses AWS Step Functions to:
- Deploy your code and dependencies to the compute group using Code Deploy. Code Deploy works by moving code from S3 to the compute group's EC2 instances and cycling the Datomic process with a newly-extended classpath, in a rolling fashion. This is much faster than cycling EC2 instances. Deploy is smart about minimizing the transfer of code from S3.
- [optionally] ensure Lambdas If you've configured Lambdas, deploy ensures an AWS Lambda corresponding to each lambda entry point. These AWS Lambdas are in fact just lightweight proxies that forward invocations to your functions running on the Datomic cluster (i.e. your code is not running in AWS Lambda). In this way your code runs near the data and cache, and without the limitations and complexities of running in the Lambda execution context.
Ions include an ion-config.edn file that specifies how to invoke your your ion code: