Live data from Hacker News

Viewing profile — monstrado

monstrado

HN member
Joined
Fri, Mar 23, 2012, 9:42 PM UTC
HN karma
415
Public activity
172 items

About monstrado

Principal Software Engineer (Data Platform) @ Fortis Games

Recent public activity

  1. comment
    Comment #45117876

    I think the point of ACP being an open protocol is so that other editors (e.g. VSCode, Neovim) can implement it as a receiver and integration with ClaudeCode/GeminiCLI/... would ju…

  2. comment
    Comment #39031748

    No write up, but the main reason was reusing the existing database we were comfortable deploying at the time. We were already using FDB for an online aggregation / mutation store f…

  3. comment
    Comment #39030038

    I leveraged FoundationDB and RecordLayer to build a transactional catalog system for all our data services at a previous company, and it was honestly just an amazing piece of softw…

  4. comment
    Comment #37987794

    One reason would be if you're already fluent in ClickHouse's SQL dialect. Although they maintain great standard SQL compatibility, they also have a great deal of special functions/…

  5. comment
    Comment #36574831

    I built an online / mutable time-series database using FDB a few years back at a previous company. Not only was it rock solid, but it scaled linearly pretty effortlessly. It truly …

  6. comment
    Comment #34348689

    As an engineer who admires the work done by DuckDB, I'm disappointed that the co-founder of its evolution is spreading FUD about competitors before its even in the competitive conv…

  7. comment
    Comment #33081864

    Disclaimer: I work at ClickHouse At a previous company, I wrote a simple TCP server to receive LineProtocol, parse it and write to ClickHouse. I was absolutely blown away by how fa…

  8. comment
    Comment #32545338

    Not sure if I hit those limits, we were at around 100 nodes and over 170-180 processes. The biggest thing we recognized was tuning the number of recruited proxies and other statele…

  9. comment
    Comment #32542536

    Running it locally is as easy as downloading and installing. Scaling FDB is a bit more of a challenge partially due to their process-per-core design decision, which coincidently he…

  10. comment
    Comment #32542488

    This project (mvSQLite) appears to have found a way around the 5s transaction limit as well as the size, so that's really promising. That being said, I believe the new RedWood stor…

  11. comment
    Comment #32540525

    This is exactly what the engineers behind FoundationDB (FDB) wanted when they open sourced. For those who don't know, FDB provides a transactional (and distributed) ordered key-val…

  12. comment
    Comment #31675202

    Curious when the folks at ClickHouse are going to decide to spin its custom rewrite of ZooKeeper in C++ (ClickHouse-Keeper [1]) out into its own separate project. [1] https://click…

  13. comment
    Comment #30856338

    Is this the project you guys referenced using Apache Arrow for?

  14. comment
    Comment #29579652

    The introduction of parallelized Parquet reads coupled with s3Cluster is really awesome. I feel ClickHouse is one step closer to unlocking the ephemeral SQL compute cluster (e.g. P…

  15. comment
    Comment #29099555

    I've had a really positive experience using ClickHouse as an InfluxDB replacement. Initially I used the BUFFERED table type to overcome the "tiny inserts" problem, but ultimately j…

  16. comment
    Comment #29099174

    While I really enjoyed this read, it'd be nice to see benchmarks which also measure Queries-Per-Second under a highly concurrent workload. I've been using ClickHouse to serve live …

  17. comment
    Comment #29098637

    This has been my experience with ClickHouse as well...that is, you can basically close your eyes while writing the schema and still maintain to get extremely impressive performance…

  18. comment
    Comment #28599455

    I'm excited for the future of ClickHouse! I'm hopeful that this move will help smooth out the rough-edges of ClickHouse, mainly around clustering.

  19. comment
    Comment #28356649

    This looks really promising! Could you provide at a high-level what this aims to offer over FoundationDB's RecordLayer[1]? [1] https://github.com/FoundationDB/fdb-record-layer

  20. comment
    Comment #28170428

    Not sure about the large stores, but i've had luck getting my balls at the local mom and pop tennis supply stores.

  21. story
  22. comment
    Comment #27436042

    The key takeaways of FoundationDB is that it is a strongly consistent KeyValue store that preserves ordering (lexicographical). Although you might consider FDB's APIs to be quite p…

  23. comment
    Comment #27426798

    Have nothing but praise for FoundationDB. It has been by far the most rock solid distributed database I have ever had the pleasure of using. I used to manage HBase clusters, and th…

  24. comment
    Comment #27082069

    I feel like OP might be thinking of gRPC, which seems to closely resemble the use case Smithy is tackling.

  25. comment
    Comment #26918960

    MinIO is an option as well and would allow you to transition from testing in S3 to your own MinIO cluster seamlessly.