Hi Muji, Is HHHypergrowth.com set up yet for paid subscriptions cause I’m glad to pay for the ability to leave comments and ask questions? I have subscribed and receive updates; however, I feel like getting into the weeds here may not be appropriate.
Thanks for your consideration,
Jason
One example question I have:
Given this quote (given taken out of context)from you Snowflake wants to be the engine that drives all analytics – both business intelligence (BI) and data science (ML/AI) – over the entire enterprise. They provide a turnkey cloud-native, scalable database platform with a heavy focus on enterprise concerns of security, governance & compliance, while having a rich ecosystem of integrations & tooling available for ingest, BI and analytics.
And
Also from you regarding Cloudflare Durable Objects provide a truly serverless approach to storage and state: consistent, low-latency, distributed, yet effortless to maintain and scale. They also provide an easy way to coordinate between clients, whether it be users in a particular chat room, editors of a particular document, or IoT devices in a particular smart home. Durable Objects are the missing piece in the Workers stack that makes it possible for whole applications to run entirely on the edge, with no centralized “origin” server at all."
This is flipping “serverless” on its head a bit, as serverless functions & microservices are all about enabling and scaling “stateless” requests (each request is self-contained, so nothing is remembered from request to request), while data is typically then persisted elsewhere, outside of the serverless environment (a cloud-hosted database, for instance). This is now keeping the data side-by-side with the application on the edge – you aren’t storing it in a separate database or API layer elsewhere. Now add in the scale and portability and geo-locationality you get from edge compute within edge networks. This feature greatly increases the sheer scale of what is possible with serverless.
It might be difficult to truly understand the potential here if you aren’t a modern developer, so let’s step back a bit. Workers are serverless functions, pieces of your API broken out into individual functions that are running in the edge. Your serverless functions can now spin up countless data objects when and where they need them, as usage demands – all still in the edge. So you have 2 different types of Workers - application instances vs data instances, with either being able to scale as needed. Worker instances can be either keeping their data objects private to just themselves, inter-exchanging data with other Worker instances, or ultimately relaying that data off into some centralized storage (out in core cloud) where needed. Each Worker instance can be shut down when idle, and can recreate itself again later on demand. Worker data objects could be moved from POP to POP, or region to region. This is cutting edge stuff from a development platform. [And, being in the business, I tip my hat to the software architecture team that designed & implemented this.].
I see the differences between Snowflake and Cloudflare.
I’m trying to get my head around how, If the Snowflake advantage in Analytics is that they store Date in parallel with compute, how is that different than Cloudflare’s abilities with their Durable Objects?
You can see why I’d be willing to pay for the answer. I’m most likely the only one stupid enough to think it’s an important question.
Jason