History is filled with bubbles and crashes. At this very moment, there are trillions of dollars invested into companies with no clear profit model who are openly and obviously fraudulent in their accounting practises. Do you think this allocation is driven by a rational consideration of the risks of investing in a business with massive obligations and no possible way to service them? Or take bit coins. They are fictional products with clear negative value, and yet some financial professional push to integrate this funny money into the real economy.
Compare and contrast: resource allocation in finance-heavy Western nations with the same in the finance-light China. It's abundantly obvious to me that, through suppressing their financial sector, China has reached a superior economic outcome than they otherwise might have. We have elected to make traders the managers of our economy, and I think they have done a clear bad job and that we aught to reassess treating their decisions with such primacy.
Kudos for the product launch. A bit curious on the product itself, to me the product seems similar to what Neon team does, except Neon doesn't touch the columnar/analytics and just focus on the rowstore. I'm wondering how do you position the product, if let say Neon team (after Databricks acq) decides to support the columnstore format?
Neon actually does have a columnstore extension with pg_mooncake today.
The key difference with pg_mooncake vs hydra is the bet on open storage formats (Iceberg).
[Joe, Hydra cofounder] Hey, thanks! There are similarities, but you’re right to point out that our focus with Hydra is on bringing columnstore-powered serverless analytics to Postgres. We wouldn’t position Hydra differently because we think it’s the right product to help the greatest number of projects and developers in a meaningful way.
I see. What's the catch on Hydra.so in terms of CAP theorem? I assume it's the C one, especially the docs mentioned about read replica. Is there any drawbacks/tradeoff that user should be aware of?
basically they separate the compute and storage into different components, where the traditional PG use both compute and storage at the same server.
because of this separation, the compute (e.q SQL parsing, etc) can be scaled independently and the storage can also do the same, which for example use AWS S3
so if your SQL query is CPU heavy, then Neon can just add more "compute" nodes while the "storage" cluster remain the same
to me, this is similar to what the usual microservice where you have a API service and DB. the difference is Neon is purposely running DB on top of that structure
So how is this distributed Postgres still an ACID-compliant database? If you allow multiple nodes to query the same data this likely is just Trino/an OLAP-tool using Postgres syntax? Or did they rebuild Postgres and not upstream anything?
You're welcome. I think for the write part, it's always back to the old classic consensus. In then end there always that distributed voting mechanism to decide the write order
All they had to do was sanitize the subdomain var to only allow values valid in host part of a URL. But also, one of the state parameter's primary uses is exactly to prevent XSRF attacks like this by using a random nonce value so that you can validate from the redirect that your system was the initiator of the auth request. The data in this state was not sensitive, so encryption is not really necessary.
Me too, I'm wondering why they decided to switch immediately. Why not provide user with a toggle to switch between old and new UI, then they can see how the data says
That's worse and confusing for the end user in the long run. It's also difficult and costly to keep two development lines in parallel. And confusing when giving support. My bank still has an old and a new site (or at least design) and that's been going for 5 years. Insane.
If you work at G, you should be able to see how D does permissions by looking at its ACL checking code (start with one of the files in the D server code that defines an op, and you can get to the permissions code pretty quickly). There's a lot of code in Colossus/D that is special because it has to be able to come up in a nearly empty cluster.
Are you talking about the 2008 financial crisis? or do you mean something else?