Here is my Ode to the Cloud 2021. Happy New Year, everyone! 🍾🥂🎆 #cloud #serverless
Two thousand twenty-one, a strange year we have seen,
Mixed with lots of highs and lows, and bags of in between.
And even though, most of us, just want to scream out loud,
Plenty of interesting things, did happen in the #cloud.
Jassy went to Amazon 'cause Bezos went to space,
And all without missing a beat, Selipsky took his place.
Munns decided startups, is where his help should aim,
So Talia, James, and others, all stepped up their game.
Forrest went to Google, and released another book,
And we're all extremely happy, with the job that Farrah took.
Rebecca joined the podcast, to chat with some cloud moguls,
Like I don't know, whaddya think, maybe @Werner Vogels?
Rick, he left Amazon, off to MongoDB,
But don't forget that AWS, acquired Stackery.
Ben started aleios, a name I do not get,
But regardless of its meaning, you ain't seen nothing yet.
Eric donned a squirrel suit, a dance off was his shot,
Bonig got the best of him, but the CDK did not.
And Julian's talks take anyone, to expert from a zero,
Plus Rosius and Ivonne are now, a serverless Takahiro.
And speaking of the CDK, there's something else with that,
A book by Höger, Bonig, Bhat, and CDKPatterns Matt.
And Matt gets a shout out, for the hours he has poured,
And the well-deserved recognition, of the Now Go Build Award.
There was lots of VC money, spread around the space,
Vendia raised a Series A, Lumigo kept up pace.
Webiny took some cash, Kong 100 million,
Cockroach did even better, now valued at 5 billion.
PlanetScale launched their database, plus announced a Series B,
Then they went, full GA, with a bigger Series C.
Vercel announced Next.js 12, for the web, an SDK,
And nabbed a Series C and D, I guess JAMStack's the way.
There were also several M&As, a few to note I will,
Like Ran and Nitzan's Cisco deal, for a cool half a bill.
A Cloud Guru and Pluralsight, have finally tied the knot,
Plus Okta and Auth0 joined, Nimbella, D.O. bought.
And as these thing were happening, it came as no surprise,
That the State of Serverless from Datadog, had usage on the rise.
Serverless is the future, it isn't hard to think,
Which is why this year, I joined the team, over at Serverless, Inc.
We launched a thing called Serverless Cloud, a monumental leap,
Plus others joined the serverless space, with promises to keep.
DataStax has Astra, Akka from Lightbend,
And MongoDB's Atlas, in keeping with the trend.
CockroachDB Serverless, launched with much delight,
Then Upstash brought some Serverless Kafka, to join into the fight.
I already mentioned PlanetScale, which seems a big to-do,
But I really wish AWS would GA, Aurora Serverless v2.
Now something else that's bubbling, a bet that I would hedge,
Is serverless compute, moving to the edge.
CloudFront Functions came along, a challenge to CloudFlare,
They just laughed, and said, "oh no, you don't want to go there!"
Pages got some updates, then Workers were Unbound,
15 minute timeouts, and upgrades all-around.
Then came R2 storage, with no more egress fee woes,
Then Images and Services, a challenger arose.
But don't forget Fastly, they said goodbye to edge cold starts,
Even argued with Cloudflare, using a bunch of performance charts.
And there are plenty of other players, doing edge compute,
But unless they really step up their game, their services are moot.
So much more has happened, like Azure Container Apps,
And Facebook became Meta, but no one gave two craps.
Knative was sent by Google, to the CNCF board,
Maybe I'm alone on this, but Kubernetes leaves me bored.
Stedi released Mappings, with events you can transform,
But we can't ignore, the AWS, product release storm.
The firehose is much too big, to list them all right here,
So here is just a smattering, of the things they did last year:
API Destinations, for EventBridge are pretty cool,
Plus S3 Object Lambdas, are a very handy tool.
Lambda got Extensions and SAM did Accelerate,
And App Runner got added to the container team's full plate.
Amazon did OpenSearch, the service was renamed,
It's not, however, serverless, for that it should be shamed.
Global tables in Dynamo, finally got CloudFormation,
No day 1 support for all these things, is a source of much frustration.
Step Functions got a Studio, a marvel of DX,
Plus 200 SDK services, what will they think of next?
Amplify made some moves, a Studio of its own,
With Ali and her team on it, the product's really grown.
The advocates launched some patterns, at ServerlessLand DOT com,
Lambda Functions got Graviton2, performance is the bomb.
Lambda got filters for SQS, Kinesis, and Dynamo,
Plus partial batch for SQS, was added to the show.
Kinesis Data Streams are now, available On-Demand,
RedShift even went serverless, to compete with Snowflake's brand.
S3 event notifications, can now go to EventBridge,
Plus some services' consoles got better, but only by a smidge.
There were also some more SDKs: Kotlin, Swift and Rust,
Plus a new, higher free tier, which really was a must.
The CDK reached v2, plus backup for S3,
In case you need more than eleven 9s of durability.
15 turned S3 and SQS, a long time there's no doubt,
And IAM, just turned 10, but I still can't figure it out.
So what else about last year, is there left to say?
How 'bout when us-east-1 went down for an entire day?
And while I'm sure they really would, like to clear the cache,
It's hard to forget about a little thing, we called Infinidash.
The idea itself was brilliant, some people got confused,
The response was less than stellar, and some egos then got bruised.
But let's focus on the positives, like debates we had with Corey,
Is it the unfulfilled promise of serverless, or the potential soon to see?
I even wrote some ditties, to help you through the mess,
Like my database cover of the Beatles' Help! and Goin’ Serverless.
So as we start the new year, let's remember all we got,
Lots of innovation and the COVID vaccine shot.
Hug your friends and loved ones, every single night,
And let's all say a little prayer, for the amazing Betty White.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Jeremy Daly

Jeremy Daly Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jeremy_daly

4 Nov 21
Yesterday I turned 43 and realized I've been in #tech for 24 years (I got paid to create my first "professional" website in 1997). Here's 24 things I've learned over the past 24 years. Perhaps you'll find them useful on your journey. 🧵
24. Plan work around your life, not life around your work - I worked 70+ hr weeks in my 20s & early 30s. While I'm sure there's a correlation between that & my "successes", there's also a lot of regret for missed time with family & friends.
23. Be a T-shaped human - There are 3 types of knowledge: the shit you know, the shit you know you don't know, and the shit you don't know you don't know. Specialize in a few things, and gain wisdom by learning the basics of many others.
Read 25 tweets
1 Oct 21
Everyone got so excited about Graviton2 Lambda functions & Step Functions AWS-SDK integration yesterday that you might have missed this one about triggering Lambda functions from SQS queues in *different* accounts. This is important, a short 🧵 #serverless aws.amazon.com/about-aws/what…
Having multiple AWS accounts to handle different parts of your application (from both a lifecycle and service perspective) isn't just good practice, it's also AWS recommended. 👍 2/9
This is because AWS account separation is the best isolation model for security, scalability, regional controls, service limit management, billing 👈, and much more. 3/9
Read 9 tweets
2 Dec 20
Very cool #reInvent session by @sliedigaws about building out distributed applications using different #EventBridge patterns. Let's recap this quickly to see how we can use them to build out our #serverless apps. 🧵
The "single-bus, single-account" pattern is a super simple way to get started, especially if you have a small team. Create logical service boundaries and use a single event bus to decouple the services. This is one of my favorite ways to prototype #serverless applications.
The "single-bus, multi-account" pattern is my go-to for larger apps, and works great for multi-team orgs w/ service-level ownership reqs. Create a *global* event bus, grant access to service accounts for putEvents, and forward events to service-owned buses for rules & routing. 👍
Read 9 tweets
16 Oct 20
Excellent post by @mipsytipsy on the future of Ops careers, even if it’s a bit critical of "Lambda: A Serverless Musical". 😉

While I 100% agree that #serverless isn’t headed towards the ridiculous notion of #NoOps, I have some thoughts on the article. 🧵
thenewstack.io/the-future-of-…
Context is *extremely* important. The repeating line in the musical of "I'm going to reduce your… ops!" is in the context of setting up and maintaining a Kubernetes cluster. If it's not obvious the first time with "Hey yo, I'm unlike containers, no patching, no maintainers"...
…then the second time around adding "No pods or orchestrators" should make it abundantly clear. Since I consider myself a #serverless purist, I try to avoid the "K" word, but the line "I know all this stuff with K8s is excitin'" should settle any further misunderstanding.
Read 13 tweets
6 Feb 20
.@alexbdebrie has another excellent post that details the benefits and downsides of using a Single-Table design with @DynamoDB. While I completely agree with him on the “benefits”, I have some thoughts on his “downsides” that I’d like to address. 🧵 alexdebrie.com/posts/dynamodb…
Downside #1: “The steep learning curve to understand single-table design”

There is no doubt that “thinking in #NoSQL” is a complete departure from traditional #RDBMS, but understanding how to correctly denormalize data is applicable to both single- AND multi-table designs.
If you are using a multi-table design in @DynamoDB that implements 3NF, then just STOP! Seriously, this is *beyond* wrong (I think presidents have been impeached for this). This is not what #NoSQL was designed for and you will get ZERO benefit from doing this. Spin up an RDBMS.
Read 28 tweets
4 Dec 19
Very interesting take from @forrestbrazeal on the new #Lambda Provisioned Concurrency. I have a few quick thoughts on this as well... trek10.com/blog/provision…
Yes, "pay-per-use" is very attractive, but I'm okay with AWS's "pay-for-value" model in #serverless environments. I don't expect the cloud to dedicate resources to me for free. I may get the benefit of warm invocations, but that's an internal optimization, not a guarantee.
Steady workloads benefit from "provisioned" capacity, not just from a pricing standpoint, but for performance as well. The "why-not-do-this-high-volume-workload-on-EC2" argument is "sometimes" valid. Provisioned Concurrency w/ Lambda is a step towards negating that logic.
Read 8 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


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

Become a Premium Member ($3/month or $30/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

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(