-
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.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
However, this is becoming tedious and error-prone and it looks increasingly desirable to duplicate the json schema hierarchy fully in CLOS. A look around turned up a WIP, json-schema2, but it looks far from complete and is undocumented.
From awesome-cl, there is json-mop but lack the experience to comment!
I see; nothing I have come across does that; though there also exists sheeple that provides a prototype-based OOP framework, but that could entail some rewrite and I'm unaware if json integration would be straightforward. It does look like it'd be simple; but no comments without the actual implementation.
The library uses my own incorporation of json-mop called json-clos, which is a re-write to make json-mop JSON encoder/decoder independent, but iirc i do some inefficient things with the mop (not that it's a problem because there is an API to generate serialization methods anyways) and I stopped developing it because I became dissatisfied with how metaclasses were being used by library authors to create an adhoc annotation system each time. (This is not some sort of aggression against CL, it's just someone should just write one library for annotations and be done with it, I gave that a try too and am willing to discuss that with people if they are interested, ie they should talk to me if they want to do it). See this but honestly I have probably changed my mind about this a lot since I last wrote in here, and I probably say some stupid things. I guess that can all be forgiven though.
The library uses my own incorporation of json-mop called json-clos, which is a re-write to make json-mop JSON encoder/decoder independent, but iirc i do some inefficient things with the mop (not that it's a problem because there is an API to generate serialization methods anyways) and I stopped developing it because I became dissatisfied with how metaclasses were being used by library authors to create an adhoc annotation system each time. (This is not some sort of aggression against CL, it's just someone should just write one library for annotations and be done with it, I gave that a try too and am willing to discuss that with people if they are interested, ie they should talk to me if they want to do it). See this but honestly I have probably changed my mind about this a lot since I last wrote in here, and I probably say some stupid things. I guess that can all be forgiven though.