4 ms·
Well, many choose to do their data-science over aws and similar, so I'm not sure there's a big different. I see you point about throughput and network load, but
by erezsh 7y ago
Well, many choose to do their data-science over aws and similar, so I'm not sure there's a big different. I see you point about throughput and network load, but part of DS is data analysis, where the work is mostly exploratory: finding connections in existing data, and working heavily with aggregated data and previews, rather than just using it as a pipeline for other systems.
I think for most JAMs the network is a bigger hindrance than the query time. So, I hope you know what you're doing.
Anyway, cool project. I'll make sure to check back in a while and see where it went. I'm working on an "adapter" (so-to-speak) that queries SQL, so maybe I'll add yours too when the time is right.
- siscia 7y agoThe advantages of using an API like these on JAM it would be that very sophisticated application could be written completely client side. Which is quite interesting IMHO. What is your project?
- erezsh 7y agoMy project is an interpreted query language that compiles to SQL (with support for several backends). It is more capable than ORMs, and provides a layer of abstraction that SQL direly needs but lacks, as well as a shorter syntax, that is in-line with other popular languages. Here is a very early version of it: https://github.com/erezsh/preql https://github.com/erezsh/preql I've kept working on it, but privately, and I'm trying to make it into a product. I will probably release it as open-source when it's ready. I still need to figure out the right license, financial model, etc.