@U07FCNURX has done something like this for his text-based game engine for Aventur Delux: https://www.adventur.no

For sure, Datomic has been a perfect database for my game, particularly because the main character has the ability to time travel.

I'm playing your game now and it's awesome! And super addictive 😅 Your writing skills might be on par with your Clojure skills! Very cool.

FYI i tried doing it but the latency was too high on local, and even higher on networking

i’ve now rewritten my ECS in pure clojure data structures backed by duratom

@U01458A7CBX do mind to share your ecs or game? What do you mean with latency was too high? Did you queue transactions till the end of a frame? Read latency ?

Yes, i queued incoming entities/messages until end of frame and processed them. Read/write latency was ok for web apps, but processing hundreds of entities per frame already took around 50-100ms or more so it was unacceptable for a networked game

But wouldn't be both things possible? Just a server using just refs or atoms for speed and at the end of a frame sending transactions to the db? Then every update tick the server sends only the transactions to the client , which does not use datomic ?

yeah, so there’s really not much use for datomic except maybe as a durable data store

the players already can get atomic updates via ecs if you structure it to emit effects to the client

As a transaction store I guess

currently im able to serve game updates at 60 fps on local so thats good enough for me

Would you mind sharing your ECS design or code or what you are working on?

i’m still in the process of rewriting it, but here’s the core https://gist.github.com/danieltanfh95/1a601090059db22a3303bd04791a7c94

And what kind of Game? I am developing a roguelike rpg

@U0ALH6R89 im writing a small hack and slash mmorpg

A slightly different take on this is using a rules engine https://github.com/oakes/odoyle-rules

What you are reading there is about datomic using an actual durable storage

The in-memory storage of datomic-pro is designed for testing, and I think it’s synchronous. I doubt much thought was given to its performance

Consider alternatives like datomic dev-local (another product which uses a local on-disk storage with cloud semantics), or if you are willing to give up history: datascript (datomic inspired, but in memory and runs on more platforms) or datalevin (durable via lmdb) or others

That said datomic-pro in-memory may be fine but it’s not the typical use

Sync writes are only a problem if they take too long :) You can always do your own queueing if you need the caller not to block