dikei

30 ms·

331.
by dikei 5y ago
I think you are confused between My Book and My Cloud * My Book: An external HDD that's attached to your computer through USB. * My Cloud: A NAS that's connected to your network through Ethernet, support SMB, FTP, NFS. There'
332.
by dikei 5y ago
I agree, you can use traditional RDBMS like Postgresql or MySQL for almost every use cases. It's just that purpose-built DBs like QuestDB can be multi-magnitude faster if your problem fit their niche.
333.
by dikei 5y ago
You just described basically how almost every write-heavy database work: write to a memory buffer then asynchronously flush the buffer to disk when convenient. From what I read in the article, it's how QuestDB works as well. The devil,
334.
by dikei 5y ago
It's in their tag line > QuestDB is the fastest open source time series database Time series data is any type of data that always has a timestamp attached to it, such as logging, metrics, telemetry, etc.
335.
by dikei 5y ago
I don't think it would matter much. Someone else would have lead the program, there were never a scarcity of talented Chinese scientists/engineers.
336.
by dikei 5y ago
Small files with S3 is both slow and expensive too. But at least one bad query won't be able to kill your whole cluster like HDFS.
337.
by dikei 5y ago
TL DR: Distributed system is hard, and Hadoop cluster are not really designed for a dynamic environment. There are as probably as many services running inside a Hadoop clusters as a Micro Service meshes, except: * The services can be huge:
338.
by dikei 5y ago
Unless you plan to throw out everything else and only ever use Snowflake, Hive Metastore is still as important as ever. Almost every Big Data tools only works with Hive Metastore (and Amazon Glue Catalog, but the compatibilities is not 100%
339.
by dikei 5y ago
Cloudera and Hortonwork promise an easy way to deploy on-premise Hadoop clusters. Yet, HDP & CDH are still too hard to maintain for the majority of companies: * Tuning for HDFS and HBase is hard. Too many files and GC pause will kill yo
340.
by dikei 5y ago
I used to use Pencil back in college, when it was still based on XULRunner, not Electron. It's a pity that the tool hasn't gained much traction in the mean time.
341.
by dikei 5y ago
Most scientific journals only do peer-review by sending articles to other scientists. These scientists, most of the time, only check for logical errors, and are not able to replicate the experiments.
342.
by dikei 5y ago
etcd is not suitable for high volume, it's built for data consistency, not performance.
343.
by dikei 5y ago
Fortunately, countries with "nuclear first strike" do not perform them liberally, due to the threat of mutual destruction. Hopefully, the same thing also applies to cyberspace.
344.
by dikei 6y ago
It's the default on KeepassXC, which replaces KeepassX and IMHO, has a better UI than the original Keepass.
345.
by dikei 6y ago
People tend to run ```mvn clean verify``` because Maven caching is unreliable, and lead to build failures. However, Bazel cache is a lot more robust, so you almost never do clean build. The only time I had to perform a clean build was when
346.
by dikei 6y ago
You have to declare all input explicitly, including your compiler and Bazel will monitor them: Any changes in input files, compilers or even some environmental variables like $PATH will trigger a rebuild. Bazel can use sandbox as an additio
347.
by dikei 6y ago
* Bazel offer much more granular caching, because a Bazel BUILD target is often much smaller than a Maven artifact. For example: a Java BUILD target is often just a single package. * SNAPSHOT maven artifact are not hermetic and not reliable
348.
by dikei 6y ago
For me, the main advantage of Bazel is speed, when properly structured and configured, a Bazel build can: * Perform incremental build a magnitude faster than Maven, zero changes build finishes immediately. * Can have global caches for all b
349.
by dikei 6y ago
I don't understand the hate for Zookeeper. Setting up a Zookeeper ensemble is not that hard, they're light on resources and and basically zero maintenance.
350.
by dikei 6y ago
To be fair, many project's Raft implementations contained errors that can and had lead to data lost, so it's not all sunshine and roses. IMHO, it's still easier to delegate the consensus problem to a third party service like
351.
by dikei 6y ago
Good binary formats with separate schema are always gonna be smaller and faster than JSON, because it doesn't have to encode field labels with every messages. JSON field names wastes so much space if your values are mostly numbers.
352.
by dikei 6y ago
There's also FlatBuffer, which is also specifically made for Gaming application by Google.
353.
by dikei 6y ago
They have different use-cases: * Arrow is columnar, batch-oriented, geared toward high throughput. * Bebob is record-oriented, similar to Avro, Protobuf or JSON, geared toward low latency.
354.
by dikei 6y ago
I like the Pi a lots, I just wish it has a built-in Realtime clock. Everytime, the Pi boots up, it need to re-synchronize time and I have to hard-code a NTP server IP, since DNSSEC won't work without correct time.
355.
by dikei 6y ago
I hope this fare better than GNU Gnash. Back in university, my friends and I had a team hacking on Gnash to try implementing an OpenGLES renderer for a class project. We never got it finished, due to the lack of documentation and our poor r
356.
by dikei 6y ago
Wasn't Sparrow got acquired then killed off by Google ?
357.
by dikei 6y ago
Since TerarkDB is latency-optimized, it would be quite interesting to test it with Kafka Streaming or Flink which are currently using RocksDB for stateful stream processing. Hopefully, that will also brings better Java test coverage and int
358.
by dikei 6y ago
If it's not using Bazel to build, it's probably not used much inside Google.
359.
by dikei 6y ago
Even when you package your dependencies with your code, unless you have policies in place and actively enforcing it, there's no preventing people from bloating the project with all kind of junks libraries. I've had to deal with le
360.
by dikei 6y ago
Actually for MySQL it depends on the storage engine, what you described is how InnoDB works. MyRocks storage, however, only appends data, and requires regular Compaction to clean up old rows, similar to Postgres VACUUM.

More ›