Clojurians Log v2
datomic
Q: where does Ion push/deploy put the jars it downloads? I want to cache these to speed up my CI deploys. I already have deps.edn jars caching so it must be somewhere else
@jaret is this info available somewhere? Or should I ask in the Datomic forum instead?
Are there any plans to support a multi-region Datomic Cloud system? I was just wondering if https://aws.amazon.com/dynamodb/global-tables/ would make it possible at all, or not, since they are only eventually consistent?
The Datomic Cloud pricing page (https://aws.amazon.com/marketplace/pp/prodview-otb76awcrb7aa#pdp-pricing) shows a lot of extra instance types (`{{t2,t3}.{small,medium},m5.large}`) with prices for the Production topology, but the CloudFormation templates from the releases page only allow i3.{x,}large.
Is that a mistake on or restriction of the AWS Marketplace solution, or is it some upcoming feature (to allow smaller instance types)?
I'm talking about the https://s3.amazonaws.com/datomic-cloud-1/cft/732-8992/datomic-production-compute-732-8992.json template for example
What’s the smallest EC2 instance I can choose to play around with Datomic Cloud in development using AWS Marketplace? i3.large is the vendor-recommended size, but that’s gonna cost me $130/month.
It switched from Solo to Production in the two screens 😊
Are you using the solo topology?
@danie, yes.
it feels like that marketplace web interface is buggy or limited and doesn't allow providing different instance type list based on whether the "Fulfillment Option" is "Solo" or "Production".
if you look into the separately released cloudformation template for the solo compute stack (https://s3.amazonaws.com/datomic-cloud-1/cft/732-8992/datomic-solo-compute-732-8992.json) and look for AWS::AutoScaling::LaunchConfigurations, then you can see that the TxLaunchConfig defines the InstanceType as "Fn::FindInMap": ["Datomic", "defaults", "InstanceType"], which is hardwired in the Mappings section of the template to be t3.small and not configurable via template parameters.
I remember vaguely that an AMI-type AWS Marketplace product can only have 1 CloudFormation configuration, that's why Cognitect had to use a root template and nest the storage and solo-compute templates below it. Maybe because of this restriction, the templates being used when you provision a system using the AWS Marketplace web interface, is slightly different from the one published on the https://docs.datomic.com/cloud/releases.html page....
@petrus ^^^
Thanks. They claim $1/day Solo topology, so trying to figure out how to get cost down to that.
just pick the t3.small instance type for the Datomic Cloud option and t3.nano for the Utility Bastion
and i can attest that the claim is true, the solo setup indeed costs only about 30 USD a month (depending on the region of course) + whatever u pay for the amount of data u use, but initially that's virtually zero.
Just making sure you know about this https://docs.datomic.com/cloud/dev-local.html
The marketplace listing page is it's own thing managed by marketplace and there are often mistakes in the dropdowns. I'll report this over to them, but its possible they reviewed the QA template instance sizes, Production template instance sizes, bastion, and Solo template instance sizes and combined them. We have our supported instance sizes documented here https://docs.datomic.com/cloud/operation/planning.html#instance-sizes
Thanks for catching this by the way!