Can Azure/AWS/GCP kill likes of DataBricks/Confluent/Snowflake over time?
Dec 19, 2020
12 Comments
Trying to understand the long-term vision of these independent companies who builds on data sets originally living in some other cloud company.
Are they under constant threat that an in-house solution by these big powerhouses can kill their business? As a client/engineering head, why would i want to spend money on two different platforms if one cloud provider is giving a similar solution? Think cost, security etc.
What am i missing that's so unique to these companies that big players cant build what they have built? #tech #bigdata #paas #iaas
comments
Customers are getting smarter and want multi-cloud strategy for their data. Databricks offers that. On top of that, their Spark is a 10-100x better/faster than what anyone else ever promises to offer you
The more stateless solutions should not be relatively a big deal to move when the business decides to move them. For more stateless components i would be more afraid of the cost in dollars/quality/security etc.
It's only a matter of time before one of the big companies copies what they do and gives their customers an offer they can't refuse.
Back in 2018 we said Snowflake is overvalued, because we know this market very well. Fast forward today, imo it's not even worth 1/10th of its valuation. The stock market is driven by retail investors feeling FOMO after seeing their friends betting on TSLA, AMD, BTC and quadrupling their money in a few months.
One other consideration for a/g/m is if it's worth it to take the chance of building their own when they already get large amounts of revenue from partnering with each of those companies.
From my experience, things like MSK aren't nearly as good as what we offer, but it's a decent enough facsimile that it eats at our sales. I don't see it as a reason for churn, just making things harder to land. It'll take a much larger investment from aws to really hurt confluent.
In general I'm bullish on confluent, this is something to be concerned about, but it's not as big of an issue as two years ago imo.
This comment was deleted by original commenter.