Hi @U06B77GQ6! Are your running in the HA configuration? That will recover automatically.

Also, make sure your DDB provisioning matches your needs, you can start by looking at https://docs.datomic.com/on-prem/capacity.html#dynamodb.

Hi @U072WS7PE! No, I am not using HA. I’m still in alpha testing for my app and we have a tiny amount of traffic and data (the entire database backed up is 336k w/o compression). I’ll take a look at those docs. Maybe we are pushing the defaults?

Thanks for the quick response. 🙂

if you are still early days I would look at Datomic Cloud -- it is less subject to this problem, and your overall AWS cost will almost certainly go down if you use ions.

Yeah, I’d like to transition there eventually. It would require rewriting my whole backend though.

I haven’t had any stability issues with the dev storage. Would it be a terrible idea to just setup frequent backups to S3 for the time being?

Probably 😂. I would recommend just turning up the DDB knobs.

Will do. Thanks for the advice @U072WS7PE. 🙂

http://datomic.com works for me

ah, its an http-only redirect

thanks nosesmith you are right but I wanted to know aside from go blocks blocking threads, in a system heavily dependent on go blocks should I be concerned about separating critical sections' thread pool from others ?

nothing critical should be in a go block

the number of threads used for go blocks is small, and doesn't grow, they are a method of coordination, not a utility for execution / parallelism

Thanks again

But can you elaborate a little more about "nothing critical should be in a go block" and "they are a method of coordination, not a utility for execution / parallelism"

Aren't they supposed to be lightweight threads in a sense?

Your comment kinda scared me, cause quite a few of my applications are actually a network of channels with async/go blocks doing almost all of the work in between them

they are for lightweight coordination of state between tasks, anything that uses blocking IO or is CPU intensive should not be in a go block

async/thread is OK for blocking IO or CPU intensive tasks

it returns a channel that a go block can park on

what happens is that when resource-intensive tasks are in go blocks, they can starve the channel operations, since the number of threads for go blocks are limited

Thanks alot

@joshkh @U09R86PA4 Datomic client is Apache 2 license, license file and source code are present in the .jar

ah didn't know that