Hortonworks

It's a tooling constraint.

During my career, I've seen it from the Teradata movement to the big data era, so you move from Teradata to Hortonworks and Cloudera on-prem.

A few years later, you then say, actually, what we need to do is then migrate to a cloud provider, so go from on-prem, big data platform to the GCP and AWS and Azure.

What I have seen and what really has kind of stayed with me is just the observation that you change your platform but a lot of the problems don't go away and that's really because it's too easy to focus and blame the challenges around tooling.

I mean, that may happen, but I don't see that as being a conscious strategy on AWS's part.

I think on the part of MotherDuck, even before all this happened, the fact that they were starting to diversify their business away from just the cloud version of DuckDB, is that we just have to learn from the history of Hadoop, where essentially it just didn't make sense for you to have Cloud Era and Hortonworks.

It didn't make sense to have two different companies.

Yeah, no, completely agree with that.