Profile picture
Ben Kehoe
@ben11kehoe
, 3 tweets, 1 min read Read on Twitter
The future of #serverless is not stateful compute. It's computeful state.
Instead of trying to shoehorn statefulness into our current stateless compute models, we should be thinking about how to bring our code closer to our data. Lambda with EBS attached is bad. Paradigms more like handing code directly to S3 to run on all your objects.
People saying “this is just stored procedures” are like the people saying “Lambda is just cgi-bin”. Sure, superficially they’ve got the same model, but the details result in very different characteristics.
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Ben Kehoe
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Related hashtags

#serverless

More from @ben11kehoe see all

Profile picture
Ben Kehoe
@ben11kehoe
One of @awscloud's biggest weaknesses is that while product teams strive to create great experiences for their services, AWS users have to use many teams' services and there's very little accountability for the cross-AWS-team experience.
AWS is the best in the world at creating autonomous teams. We’re asking AWS to figure out how to scale their customer obsession in a way that cross-team feedback is appropriately prioritized.
We’re glad docs are in GitHub, but we want PRs to get addressed faster. We shouldn’t have to go to 90 individual teams to beg them to do that! There should be customer advocates at AWS that see what we see, and are empowered to help make it happen
Read 6 tweets
Profile picture
Ben Kehoe
@ben11kehoe
Statelessness is not the critical property of #serverless compute, it's ephemerality. Being positively limited in duration means the provider can *transparently* manage the platform, no scheduled (or unscheduled, in Fargate's case) downtime needed.
Currently, most serverless compute is time-limited, run in response to fixed-size(-ish) events. But finite-input-limited compute is possible; this is AWS Batch's model.
Several acadamic papers, including the recent one from Berkeley, have equated serverless with existing FaaS models and complained of its inapplicability to big data processing. I think this is a failure of imagination.
Read 5 tweets
Profile picture
Ben Kehoe
@ben11kehoe
I am wholly against this mindset. It downplays the operations and maintenance burden assumed by building something yourself. Looking at TCO, it's almost always a better option to accept the 80% fully-managed-service solution than take on all the extra burden of a custom build
By building something yourself—and even before that, setting up infrastructure like k8s b/c you're *planning* that you'll want to build things yourself—you're spending resources on technology problems. You should instead by looking for ways to keep focus on business problems
Say a provider is lacking a feature that you want in order to build some business value. First question: can you work around it, using fully managed svcs? The answer is usually yes. It often takes some duct tape, but my experience says it almost always still works fine...
Read 6 tweets

Related threads

Profile picture
Paul Johnston
@PaulDJohnston
"Serverless scaling" in this context means it can scale from zero to *concurrency limit*. That's fine... sort of. But to be truly #serverless you need..

... rapid cold starts

At present, Cloud Run cold starts are too long (unless I'm missing something) to be truly serverless
Yes, it depends on the underlying container here and yes the developer is responsible for that but even the "Hello World" takes too long for me (well over a second).

In the Lambda world it is in the few hundreds of ms for a well written usable function (even over API Gateway).
Yes I'm holding it to a higher standard. It doesn't mean it's not usable though. I think it has real promise. Lots of opportunity to build some amazing solutions with it.

Things you should not do: dump existing containers into it ... KNOW YOUR TOOLS!
Read 3 tweets
Profile picture
Matt Weagle
@mweagle
1/ Twead incoming...
2/ I have some #serverless localhost v. cloud Dev n' Testing thoughts. As a teaser:
3/ Disclaimer: not everyone, not all the time, not always possible, hyperbolic by intent. But I think it should be the default position.
Read 19 tweets
Profile picture
Gal Bashan
@BashanGal
#serverless advocates - we are doing something wrong. I have been putting this off for a long time but I really think it is important and has to be said. Warning: LONG thread.
The trigger for this thread was a talk I gave at #DevOpsDays Edinburgh. It wasn't the talk per-say, but the whole conference experience (which was awesome, but that's a topic for another thread).
Here I am, with around 200 people who really care about the DevOps culture and practices - and so little of them has any experience with serverless tech.
Read 23 tweets
Profile picture
Seven Archangels
@realDepIorabIe
#Bring the Pain
#FridayFeeling #AmericaFirst #BuildtheWall #QAnon #RedNationRising #POTUS
Read 4 tweets
Profile picture
Paul Johnston
@PaulDJohnston
THREAD:

So, let's have a quick chat about CI/CD and #serverless.

This will be more "overview" than in depth (it's twitter after all)
CI and CD* are not the same thing

*and there are 2 types of CD
CI is Continous Integration

When multiple developers are working on one project, at some point they have to come together and combine their efforts...

...therefore Integration

And that happens continuously over a project
Read 21 tweets
Profile picture
Matteo Figus
@matteofigus
For me a serverless (S-) architecture is much more than a event-driven function as a service (FaaS)...

(Thread)
#serverless #faas #architectures #thread #lambda #fastMovingTeams #ownership #devops
A S- architecture is an abstraction on top of a (potentially very complex) infrastructure, so that devs can focus on building great features and products and run their code in production without focusing on boring configuration and scalability.
This doesn't mean there are no servers and there is no care for infrastructure: quite the opposite indeed.
Read 24 tweets

Trending hashtags

#CRISPR #SaudiArabia #Monsanto #Erdogan #chemicals #Diverse #ParkinsonsDisease #nailedIt #EarthStrike #3giugno #Mass #MBS #museums #EcologicalLimits #Saddam #Khashokggi #Catholics #faas #MohammedBinSalman #fastMovingTeams #PRAY #Saudi #PoisonFree #Kushner #London
Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!