esammer.bsky.social
CEO @ Decodable. Systems, databases, stream processing. O’Reilly author, ex-Cloudera, Splunk, Rocana, and others.
https://www.decodable.co
25 posts
3,619 followers
112 following
Regular Contributor
Conversation Starter
comment in response to
post
The consensus seems to be SaaS or Fully Managed SaaS. Really appreciate everyone weighing in on this. The internal debate remains lively. 😉
comment in response to
post
It's not often, but more than you might expect. Varies by role and how hot the market is. Some people just live life dangerously.
comment in response to
post
This is approximately what we do today, yea. "Traditional" just has this weird connotation of "legacy." It's also not specific or descriptive. "Normal" also makes BYOC sound abnormal which it is increasingly not.
comment in response to
post
Is it actually dedicated or is it multi-tenant? Ours is the latter.
comment in response to
post
Some terms people use:
- (Full, Hosted, Managed) SaaS
- Serverless
The confusion is that our BYOC option can also be managed by us. 🤷♂️
comment in response to
post
Ok, fair question! I think it's because of the way it's used. Unmounting and remounting it in a failure case is weird and slow and subject to bad corner cases (local i/o abstraction over a network service). Same issues as NFS, plus or minus.
comment in response to
post
I was lucky enough to see a very large, very high throughput, very margin-sensitive system, with enterprise SLAs in the cloud that informed my most recent opinions on this. Those include never using EBS. Even there, and to the earlier point, a storage service w/ ephemeral disk backed by s3 = better.
comment in response to
post
Yes, totally agree.
comment in response to
post
Yes. This.
comment in response to
post
I'm not shilling for rocksdb or anything. Flink's state backends and checkpointing system are due for an update. The Flink 2.x work might be The Way (too early to tell). Just suggesting we don't throw the baby out with the bath water on this one.
comment in response to
post
There are valid questions about how things like rescaling and restoration work, but I think there are good patterns for dealing with this that get into the design of the storage layout and primitives. TLDR, it should be possible to page in/flush chunks rather than everything, but that's obvious.
comment in response to
post
Half of what I talk to technical founders about is learning and building this stuff for the first time. I wish I had these things two companies ago.
comment in response to
post
Thanks for including me. Great list!
comment in response to
post
Unfortunately things I'm not yet ready to talk about. Database stuff.
comment in response to
post
Ok, so have you met my friend `#[async_trait]`?