Very interesting. I maintain the https://github.com/jillesvangurp/es-kotlin-client and I've actually been thinking of creating a multiplatform client as well lately. My current client piggybacks on the Java client. But with opensearch emerging as a standalone fork that isn't compatible with the ES Java client, it is tempting to invest in multiplatform. Especially now ktor native servers are also becoming a thing. Plus having a client ready to go for kotlin-js and wasm would be nice too.
Looks like we have similar ideas about providing nice DSLs but slightly different approaches. I try to stay close to the json DSL by essentially mirroring that with Kotlin type safe constructs. I rely a lot on interface delegation to Map objects for this.
a
Alexander
11/01/2021, 4:58 PM
I've seen your project before started my own.
And its true I had slightly different vision on the Elasticsearch query API.
I originally didn't want to use Java rest client as it can be incompatible even between major versions (this is what we suffered with Python client).
Alexander
11/01/2021, 5:06 PM
My company has a monolithic web-application that heavily uses Elasticsearch. And we made a decision to separate search functionality into a microservice. I insisted it should be written in Kotlin )))
As pythonistas we all really like
SQLAlchemy
so this greatly influenced our project.
👍 1
s
suresh
11/01/2021, 7:31 PM
Just curious, is this api inspired by exposed ?
a
Alexander
11/01/2021, 9:20 PM
Mostly I was inspired by
SQLAlchemy
when wrote elasticsearch query api for Python. But yes, I looked at