Profile picture
Kelsey Hightower @kelseyhightower
, 3 tweets, 1 min read Read on Twitter
The more time I spend writing Serverless functions the more I understand why the container image is overkill.
The only valid use for a Serverless container image is to workaround limited language support for a given platform.
I wanted a container image due to lack of transparency. This is something that FaaS providers can address by open sourcing their function wrappers and documenting their execution environments.
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 Kelsey Hightower
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!

More from @kelseyhightower see all

Profile picture
After building my first custom Lambda runtime, it's safe to say AWS hit a home run, the Lambda Runtime API is a game changer. aws.amazon.com/about-aws/what…
Given the combination of the Lambda Runtime API and Lambda Layers I no longer believe adding support for containers would add any additional benefit to Lambda.
The Lambda Runtime API provides a major benefit over containers for Serverless workloads: a well defined and opinionated runtime API for getting work done.
Read 3 tweets
Profile picture
Paul’s post highlights how FaaS platforms, and the current state of their execution environments, influence how you write and deploy code.
If you breakdown Serverless into two parts: “use managed services for everything” and “use a pay per use code execution environment”, you may find FaaS isn’t the only valid compute option in a Serverless architecture.
If Heroku, AppEngine, or Fargate offered the same pricing model as Lambda, while eliminating the side effects of scaling to zero, would we consider them suitable replacements in Serverless architectures?
Read 3 tweets
Profile picture
Think of the live demo as end to end integration tests. I'm essentially running them manually on stage. It's much easier for me to make unit tests work vs fully automated, end to end deployments, backed by real infrastructure, networking, and security.
Many of my open source contributions, libraries, and tools that I host on GitHub were created while working on a live demo. It takes a lot of work to make things look simple in front of thousands of people.
The other by-product of live demos is end to end documentation such as the Vault on Kubernetes tutorial. I had to create a new automation tool, vault-init github.com/kelseyhightowe…, just to improve the UX of such a complex deployment. github.com/kelseyhightowe…
Read 5 tweets

Related threads

Profile picture
#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
I’ve been thinking a lot about serverless architecture and I’ve realised what bugs me about it.

This is gonna be a long one. Not gonna lie, I wrote a draft first. If I hadn’t, this thread would end right before it got interesting because I’d get distracted by a butterfly.
At its heart, serverless/FaaS/lambda/whatever-you-call-it works for me because it ties action to cost. The more I do (or the more inefficiently I do it), the more I pay. More users, more money. @gojkoadzic wrote about this years ago. It’s not new. gojko.net/2016/08/27/ser…
The problem, I find, is that in doing so, it breaks your application apart. Now we have many applications. They all work with HTTP, or message queues, or some other data interchange layer I don’t care about when I’m designing functionality for a user.
Read 20 tweets
Profile picture
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
Profile picture
Time to talk more about Dark (darklang.com), and making coding 100x easier.
Our aim with Dark is to make it 100x easier to code, for existing developers. (Side quest: making it 100x easier to code will _also_ make it easier for way more people to learn to code).
How can coding be made 100x easier? By removing 99% of things a coder has to do, that is: find all the accidental complexity and remove it.
Read 10 tweets
Profile picture
Writing Myths #3 Writing Portfolios are the magic way into the industry!!
Get a portfolio said the writing panel/advice/speaker in what is the latest throwaway simple advice that instantly builds a career…. So, let’s talk about them.
1/24
1)Portfolios are NOT magic. Simply having one doesn't get you a job. Tey are a tool to be used in chasing work and an increasing number of employers ask for them. Having one can be very useful, but just putting some bits of writing in the same place does not = instant career.
2) People tend to read your email first, then your c.v. and then portfolio. Mess up stages 1, or 2 and 3 may well not matter. Always rework your email, c.v. and portfolio for EVERY application. Focus on what matches that job/company.
Read 60 tweets
Profile picture
THREAD: A good practice is for each AWS Lambda function to do one thing rather than bundle all functionality into one function.

Why?
A quick answer is that the smaller the Lambda function, the faster it will load and the quicker it should run (depending on libraries etc), but that's very simplistic
Let's take a slightly more businesslike view of #serverless
Read 20 tweets

Trending hashtags

#GoodbyeDemocrats #biomedicalization #LUNAR #serverless #haskell #growth #USA #BinLaden #gameswriting #selfish #Puranas #Apple #insurance #RigVeda #GRAConsultation #ComplimentsOfTheSeason #political #antichoice #relationships #Reform #YJweek18 #Rogue #Christian #MBD #deepfakes

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 and get exclusive features!

Premium member ($3.00/month or $30.00/year)

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!