Return Maps

Most Datomic queries return tuples, but sometimes you just want maps.  Today's release of the Datomic Cloud client library adds return maps to Datomic datalog.  For example, the following query uses the new :keys clause to request maps with :artist and :release keys:

[:find ?artist-name ?release-name
:keys artist release
:where [?release :release/name ?release-name]
[?release :release/artists ?artist]
[?artist :artist/name ?artist-name]]

Running against the mbrainz-sample database, this query returns:

#{{:artist "George Jones" :release "With Love"}
{:artist "Shocking Blue" :release "Hello Darkness / Pickin' Tomatoes"}
{:artist "Junipher Greene" :release "Friendship"}

To try return maps, you can


HTTP Direct for Datomic Cloud

    Datomic Cloud is designed to be a complete solution for Clojure application development on AWS. In particular, you can implement web services as Datomic ions behind AWS API Gateway.

    The latest release of Datomic Cloud adds HTTP Direct, which lets you connect an API Gateway endpoint directly to a Production Topology Compute Group as shown below: 

    HTTP Direct provides better performance and simpler operation than AWS Lambda Proxy Integration. The latter option continues to be supported on the Solo Topology, which does not include the Network Load Balancer required for HTTP Direct.

    To try out HTTP Direct:
    1. Get the latest release of Datomic Cloud.
    2. Work through the HTTP Direct Tutorial.


    Valcache for Datomic On-Prem

    Everything gets better when data moves closer to processing. Datomic can extensively cache its immutable data without concern for coordination or invalidation. With the 'valcache' feature in today's Datomic On-Prem release you can use your local SSDs as large, durable per-process caches, on both transactors and peers. Valcache can improve performance, reduce the read load on storage and stay hot across process restarts.

      To get started with Valcache for  Datomic On-Prem:


      Datomic Query Groups

      Datomic system can grow to meet the needs of your applications with query groups.

      Query groups provide one or more applications in a system with independent, elastically scalable query resources and working set caches. You can deploy different Datomic Ion applications to different query groups.

      Query groups can host different application development stages, each running their own revision of an Ion application.

      To learn more about query groups, read the new Growing Your System documentation.

      Datomic Cloud on AWS Marketplace
      Datomic Cloud on AWS Marketplace


      Parameterizing Datomic Ion Applications

      Today's Datomic Cloud release provides an easy way to parameterize ion applications.


      At runtime, applications need access to configuration data such as the name of a Datomic database. There are several challenges to consider:

      • Configuration values have a lifecycle that is independent of application source code. They should not be hard-coded in the application, and should be managed separately from source code.
      • Applications need a way to obtain their configuration values at runtime.
      • Configuration values may be sensitive, and should not be stored or conveyed as plaintext.
      Parameters are a solution to these challenges.

      Ion Parameters

      Before running your app, you store parameter values under hierarchical keys in AWS Systems Manager Parameter Store. At runtime, your app uses our new APIs to form the keys and read the values. This provides:
      • independent lifecycle for parameter values
      • encryption for sensitive data
      • granular IAM permissions

      Get Started

      To get started using Datomic's parameter support:

      2 of 12