21–30 of 32 posts
One of the founders here. Thanks to the community for all the support and encouragement. We couldn't have gotten this far without people getting excited about our software. 2015 is going to be a great year for open source time series databases!
One of the founders here. Thanks to the community for all the support and encouragement. We couldn't have gotten this far without people getting excited about our software. 2015 is going to be a great year for open source time series databases!
How does your offering compare to KX ? http://kx.com/ . Do you see as a direct competitor or rather a completely different product? Do you see yourself competing in the financial sector soon?
We're open source and want to make sure we hit use cases in DevOps, metrics, and sensor data. The financial market data use case is a nice to have for what we're building, but it's certainly not what we're optimizing for.
If we compete in the financial sector with them, it won't be for a while.
Earlier quoted context omitted.
How does your offering compare to KX ? http://kx.com/ . Do you see as a direct competitor or rather a completely different product? Do you see yourself competing in the financial sector soon?
KX seems to be much more focused on the financial sector use case. It's also closed source and has been around for a long time. We're open source and want to make sure we hit use cases in DevOps, metrics, and sensor data. The financial market data use case is a nice to have for what we're building, but it's certainly not what we're optimizing for. If we compete in the financial sector with them, it won't be for a whi…
It is definitely more finance oriented, though Kx are making moves towards other application areas. Another difference I'd highlight is that Kx concentrate on the core database itself, esp. performance and expressiveness of the query language, and leave things like GUIs and admin add-on tools to partners (like first derivatives and aquaq).
kdb does just fine with metrics and sensor data. Personally, I would argue that it's weaker on string handling though, which can hurt in certain use cases.
I doubt it'll go open source any time soon. However, it being around a long time is something salescritters can spin to wonderful effect re stability, support, etc etc. ;-)
I think there are fine application areas in finance that you should consider -- just consider the many areas where the core problem isn't related to juggling TB of market data ticks coming off the exchanges.
Earlier quoted context omitted.
KX seems to be much more focused on the financial sector use case. It's also closed source and has been around for a long time. We're open source and want to make sure we hit use cases in DevOps, metrics, and sensor data. The financial market data use case is a nice to have for what we're building, but it's certainly not what we're optimizing for. If we compete in the financial sector with them, it won't be for a whi…
Disclaimers: I was CTO@Kx for a while, but also like InfluxDB :-) It is definitely more finance oriented, though Kx are making moves towards other application areas. Another difference I'd highlight is that Kx concentrate on the core database itself, esp. performance and expressiveness of the query language, and leave things like GUIs and admin add-on tools to partners (like first derivatives and aquaq). kdb does jus…
If KX is making moves into sensors are they competing more with Informix? Or maybe Vertica?
One of the founders here. Thanks to the community for all the support and encouragement. We couldn't have gotten this far without people getting excited about our software. 2015 is going to be a great year for open source time series databases!
Looking forward to seeing how this all plays out. Best of luck!
Hi, I'm on os x using macport. What are my options for installing InfluxDB?
Earlier quoted context omitted.
Disclaimers: I was CTO@Kx for a while, but also like InfluxDB :-) It is definitely more finance oriented, though Kx are making moves towards other application areas. Another difference I'd highlight is that Kx concentrate on the core database itself, esp. performance and expressiveness of the query language, and leave things like GUIs and admin add-on tools to partners (like first derivatives and aquaq). kdb does jus…
Thanks! That last use case you talk about is the one I'm definitely thinking is what we won't be pursuing. Lots of money there, but hard to come after an entrenched competitor that is heavily optimized for it ;) If KX is making moves into sensors are they competing more with Informix? Or maybe Vertica?
Vertica is seeing use for more historical stuff, and where the time series queries are pretty simple. Informix time series is doing ok, and has better support for rich queries, but isn't really playing realtime. MemSQL has the realtime perf (hi guys!) but needs to beef up on expressiveness. SAP HANA could do it, but not seeing major uptake there.
Still seeing lots of ad hoc solutions, and the expected experimentation with the usual hadoop menagerie (spark is helping make that practical).
The sensor stuff gets interesting at scale. Individual sources may not be producing data that quickly, but in aggregate it can be entertaining volume. Esp. when it comes to mobile things, and correlations become interesting to look at.
Deep thoughts need to wait for the coffee to kick in.
I suspect we'll see a lot of reinvention of technology to cope with these problems; perhaps even open source..
One of the founders here. Thanks to the community for all the support and encouragement. We couldn't have gotten this far without people getting excited about our software. 2015 is going to be a great year for open source time series databases!