Clojurians Log v2

Good Morning!

Morning

Aloha!

Morning!

howdy

Heyooo

morning

useless meeting about details that don't matter yet.

good morning!

’morning

morning

panicked clients this morning

Morning

I read picknicking clients and I feel bad now.

Why would you feel bad if your clients are picknicking? (except for the fact that it might be a bit cold at the moment)

technical question... I just have been reading about DynamoDB and the docs says it can't do joins... but I think I do need them (as I have entities that are related to each other). so not an option then?

and go with a SQL or Graph DB instead?

ps. we aren't talking lots of data... if we ever hit 1G i'd be surprised.

you'd have to do the joins in application code, or what usually happens is that you write out your data as you want to query it (do the joins up front)

this is how Cassandra works as well

'noon

what about using lambda's that do the joining of the data? is that something that people do?

that would ruin the speed of the system

dynamo/cassie presume that storage is cheap and you know what you want to query

so you basically pre-materialise your views on write

ok, ta

But... 1G. you could also just use sqlite

I'd only use cassie/dynamo if the volume of writes you have would overwhelm a RDBMS that has to update various indices on writing

and @mpenet speaks wisdom (missed your 1GB thing)

Cassandra for 1G is a bit like using a nuke on a nail

and he improves my c* usage 🙂

if you wish to atomise the nail it is the right solution 😉

@thomas You could probably look into Crux? AFAIK it now support light-weight backends (e.g. something JDBC based) so it might be a possibility for efficient queries.

@thomas I concur with the others, you probably want to use a relational db 🙂 in my experience, trying to do relational stuff with a non-relational db tends to be much worse than setup hassle of any SQL database

Love me some postgres

we are working with an external party to implement stuff. so if I introduce Crux or anything else fancy it will become just more complicated for them and thus cost more. so not really an option unfortunately.

sqlite is really good, if you're sure it's going to be "small data", just use that

a bit like postgresql "light"

sqlite is very, very good. I've been happy with where we've used it

is anyone using H2? is it somehow significantly different from sqlite?

appart from providing server-mode and, I believe, encryption?

not sure h2 support json fields, but I could be wrong

I always thought that it’s not possible to use more than one consumer for sqlite databases (e.g. application + developer tools) but apparently it’s also supported

documentations says it supports JSON

I think concurrent writers can be an issue with sqlite

not sure, it's been a while

h2 is a very very good database

…but bound to jvm

agreed

my go-to is PostgreSQL. Love me some PostgreSQL.

My go-to is Datomic, but it's definitely not light nor well-known 😄

I wonder could h2 be compiled using Graal

I was thinking about Postgres as I know it and it is available on AWS.

didn't see sqllite in the list.

ain't cheap iirc

but then again. for 1G

@dharrigan hsqldb can be compiled with graal: https://github.com/babashka/babashka-sql-pods/

@thomas sqlite wouldn't have a server as such so wouldn't be an AWS service

1gb? Duratom :)

I use sqllite on the client for storing stuff temporarily at the moment as there was an Expo package for it

@thomas I don’t think sqlite can be operated as a service 😄

no, it can't I figured that out as well... going with postgers at the moment.

there’s a saying “Nobody ever got fired for choosing Postgresql”

Unfortunately that is also true of many technologies that suck ^^

Morning

crux on confluent cloud is quick and semi-easy to setup. runs on AWS and is not overly expensive. When you’re running the service on an EC2 host then you could try my experimental DynamoDB backend for crux transactions.

I think that is misleading. You can join data or 3-tuples left and right in datomic it’s just no your RDB database join. If in doubt, then it’s rather cheap to do iterator over the resultset and query another n times etc. Depending on how you organize your code. With datomic ions you can even deploy your code “into” datomic (code near data) for ultra-fast access to the db.