-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Actually ... it works. I'm calling Clojure from Kotlin in Spring Boot and it integrated very nicely.
You have to export the code to make it callable, and I had to write some adapters on the Kotlin end. But very doable for integrating if you need to.
export:
https://gitlab.com/crossref/rest_api/-/blob/main/src/cayenne...
convert:
https://gitlab.com/crossref/manifold/-/blob/main/src/main/ko...
Actually ... it works. I'm calling Clojure from Kotlin in Spring Boot and it integrated very nicely.
You have to export the code to make it callable, and I had to write some adapters on the Kotlin end. But very doable for integrating if you need to.
export:
https://gitlab.com/crossref/rest_api/-/blob/main/src/cayenne...
convert:
https://gitlab.com/crossref/manifold/-/blob/main/src/main/ko...
I'll do my best but there might be better explanations around the web.
I think an illustrative example would be this repo:
https://github.com/cognitect-labs/anomalies
These are basically re-usable, namespaced keywords. You might decide to use them or something similar in your program/system and some people do. Pretty neat: Their semantics are documented in the readme and the little bit of code in the repo defines a spec here https://github.com/cognitect-labs/anomalies/blob/master/src/....
You can read it as: any map that has these keywords as defined in the spec is an "anomaly".
Specs are open, non-exclusive so you can add more stuff to your structure and they still conform. (Note that the double colon before the keywords just mean "the current namespace defined at the top".)
Note that you don't need to define a spec for namespaced keywords. It's just a utility that leverages them. By themselves they already say "I can be used in a global context".
---
These keywords can be used from anywhere and by themselves. You don't need to carry around their context for them to work or have meaning. To contrast: for example a JSON field in a nested context might only make sense in that specific nesting context. Clojure namespaces are by convention globally unique.
Some examples:
- `:my.domain.accounting/refnumber`
- `:my.domain.ui/color` defined as `(or :my.domain.ui/rgb :my.domain.ui/hsl)` etc.
- `:my.domain.person/name` defined as a string if at all
- `:my.domain.event/type`