proddata

7 ms·

1.
by proddata 5y ago
CrateDB DevRel here :) > databases providing an abstraction through the Postgres wire protocol I would not call it an abstraction, if one has a full parser, analyzer, planner and execution engine. It is just a common language ;)
2.
by proddata 5y ago
Not being able to keep up with the incoming data. But 100-200Hz I'd consider fine for most
3.
by proddata 5y ago
What do yo mean by high-frequency data? 100Hz, 1KHz, 100KHz? For that kind of use cases many time-series DBs break apart. We have customers storing multiple millions of high frequency measurements per sec in arrays. I would say, Postgres is
4.
by proddata 5y ago
Sorry, mixed up the number 2GB memory (0.5GB heap). So 1:500 is correct
5.
by proddata 5y ago
Most of CrateDB clusters run on cloud providers hardware (azure, aws, alibaba). Using EBS (GP2 or now GP3) is also quite common. Due to the indexing / storage engine, gp disks are typically sufficient and faster disks have little to no
6.
by proddata 5y ago
- Depends - Just inserting, indexing, storing and simple querying can be done with little memory (i.e. 1:500 memory-disk-ratio 0.5GB RAM per 1TB disk). Typical production clusters with high query load are in the 1:150 range i.e. 64GB RAM fo
7.
by proddata 5y ago
> is an OLAP database a common go-to for longer-timescale analytics (as in [1])? I would not consider Clickhouse or CrateDB "classic" OLAP DBs. I can speak for CrateDB (I work there), that it definitely would be able to handle
8.
by proddata 5y ago
That article takes various concepts from typical TSDB solutions and seemingly only looks at the bad sides. Time series data has many different forms, not every form works for every TSDB solution. For the 3 caveats at the top, there are alre
9.
by proddata 5y ago
Sorry, but this is not true at all. Some of the biggest changes within ES come from Lucene, like _massive_ reduction in memory footprint, enabling ES to use cases not even possible before.
10.
by proddata 6y ago
If you are looking an OSS ES replacement, CrateDB might also be worth a look :) Basically a best of both worlds combination of ES and PostgreSQL, perfect for time-series and log analytics.
11.
by proddata 6y ago
Yes, we have customers using CrateDB as part of their proprietary product. Also the SSPL is so vague, that we probably would not only have to release CrateDB itself - which we already do, but also everything we use for the services we provi
12.
by proddata 6y ago
The thing is, that all the arguments they now bring up for the move, have been true in 2018 as well ...
13.
by proddata 6y ago
> So, they don't run Linux, don't use glibc? That can't be all that common? (I mean sure, there's the bsds.. But still..). We do run Linux :) But there is a difference between building on and building with.
14.
by proddata 6y ago
> This begs the question: isn't "a restrictive OSS licence" not less "fully open source" than a more permissive licence like GPL, MIT or BSD? We gonna change CrateDB fully to Apache License v2 ;) I would say that
15.
by proddata 6y ago
> If your business model cannot survive when a critical upstream piece of your infrastructure moves to GPL, you probably have a bad business model to begin with. To be clear CrateDB started out as OSS and we decide to stay OSS. Elasticse
16.
by proddata 6y ago
Fair point - I will review this with our marketing and get that fixed
17.
by proddata 6y ago
Many reasons actually ... - Scalability CrateDB is built for horizontal scale from the ground up on top of distributed technologies. We have customers using clusters with 80+ nodes in production for many years now. Timescale just released t