Immediately something felt off when I saw the AI generated cover photo. Hard to describe, but I immediately profile a page online when I see clear AI slop. I wouldn't want to taint something that I had taken the time to write with something so... low effort.
The comments are pretty interesting. There was a discussion about how different they were trying to make the public image about their tech look compared to their actual usage - supposedly to entice more engineers to join.
I think its interesting to attach any company prominently to a database technology since theoretically there would be varied use cases across an org like uber which would likely want different technologies depending on those use cases. Of course they might just have 50 other articles like this for all the other tech they use.
> The [Odin] platform supports 23 technologies, ranging from traditional online databases such as MySQL® and Cassandra® to advanced data platform technologies, including HDFS™, Presto™, and Kafka®.
Every six months, I explore switching from MySQL to something new for a more modern tech stack. However, MyRocks (https://docs.percona.com/percona-server/8.4/myrocks-index.ht...) is truly impressive. It allows me to efficiently compress my text-rich rows.
Read the parent post to this one, AI slop has an uncanny valley associated with it. Somehow it sticks out like a sore thumb but i can't put my finger on why.
I don't know, I didn't spot that this was AI generated. Perhaps because there's some truth that MyRocks is actually really good at compression.
Back when I was exploring migrating from TokuDB to MyRocks the only problem with it was that it didn't have a file per partition, meaning if you were doing retention you couldn't just drop old daily partitions cheaply.
I’m amazed how I’ve worked with all of the critical technologies in this article, I’ve dealt with the same or similar concerns, and yet the author or authors have written this engineering blog post in such a way as to not convey anything meaningful at all.
One part of it is the constant talk of high level abstract infrastructural pieces, and the other is bad product or concept naming.
Odin, “the controller,” the constant obsession with certain engineering orgs to use words like “plane,” and likewise, “fabric” was used at a previous org I worked for.
I’m sure Uber is doing Real™ Work, but this kind of crap sets off all my wank and bullshit alarms.
It’s just clients talking to servers talking to servers talking to proxies talking to servers talking to databases talking to replicas. Can you please stop with the false high engineering bullshit?
the plane separation is important though, you want to ensure your control messages always go through, like how servers have a dedicated line for management.
I ran this through ChatGPT and it found a few grammatical errors - that I agree with - and awkward wording. Usually AI generated text doesn’t have these types of errors.
It reads like a standard corporate blog post. You can find plenty of those on AWS blogs that were written before LLMs were publicly available.
I think you feel that way because it's written more in a whitepaper tone instead of a blog article tone. If you're not deeply mired in distributed relational database systems, you likely won't get anything out of it.
It's not written like a "fable" as most technical blog articles that do well on HN tend to be. There is no great philosophical life-insight that the authors stumbled upon while doing this mundane technical thing.
In shops that have been on MySQL for thirty years, people probably continue to say "MySQL" even though it's MariaDB. They have things named after MySQL, like host names, configuration files, lines in configuration files, discussion channels and mailing lists, and whatever else.
Readit News
Deleted Comment
* Why Uber Engineering Switched from Postgres to MySQL (2016) https://news.ycombinator.com/item?id=26283348
* Upgrading Uber's MySQL Fleet https://news.ycombinator.com/item?id=41836748
I think its interesting to attach any company prominently to a database technology since theoretically there would be varied use cases across an org like uber which would likely want different technologies depending on those use cases. Of course they might just have 50 other articles like this for all the other tech they use.
> The [Odin] platform supports 23 technologies, ranging from traditional online databases such as MySQL® and Cassandra® to advanced data platform technologies, including HDFS™, Presto™, and Kafka®.
Deleted Comment
Back when I was exploring migrating from TokuDB to MyRocks the only problem with it was that it didn't have a file per partition, meaning if you were doing retention you couldn't just drop old daily partitions cheaply.
One part of it is the constant talk of high level abstract infrastructural pieces, and the other is bad product or concept naming.
Odin, “the controller,” the constant obsession with certain engineering orgs to use words like “plane,” and likewise, “fabric” was used at a previous org I worked for.
I’m sure Uber is doing Real™ Work, but this kind of crap sets off all my wank and bullshit alarms.
It’s just clients talking to servers talking to servers talking to proxies talking to servers talking to databases talking to replicas. Can you please stop with the false high engineering bullshit?
It reads like a standard corporate blog post. You can find plenty of those on AWS blogs that were written before LLMs were publicly available.
It's not written like a "fable" as most technical blog articles that do well on HN tend to be. There is no great philosophical life-insight that the authors stumbled upon while doing this mundane technical thing.
The cover image is however:
> Cover Photo Attribution: The cover photo was generated using OpenAI ChatGPT Enterprise.
Deleted Comment
Deleted Comment