Discover and read the best of Twitter Threads about #serverless

Most recents (24)

re:Invent starts tomorrow, so let me round up the biggest #serverless related announcements from the last 2 weeks (I know, crazy!) and share a few thoughts on what they mean for you.

Mega 🧵If this gets 168 retweets then I'll add another batch!

#serverless #aws #reinvent
1. Lambda released Logs API which works with the Lambda Extensions mechanism that was released in Oct. This lets you subscribe to Lambda logs in a Lambda extension and ship them elsewhere WITHOUT going through CloudWatch Logs

aws.amazon.com/about-aws/what…
Why is it important?

a. it lets you side-step CloudWatch Logs, which often costs more (sometimes 10x more) than Lambda invocations in production apps.
b. it's possible (although not really feasible right now) to ship logs in real-time
Read 45 tweets
X: when would you NOT use #AppSync?
me: since AppSync gives you managed #GraphQL server as a service, so if you need a REST API instead then you won't use AppSync. Also, you wouldn't use AppSync if you need GraphQL/Apollo features that are not supported by AppSync
X: what sorta features are you talking about?
me: you can't define custom scalar types (e.g. LatLon is a popular one), and implementation-specific features like Apollo federations for schema stitching, or utilities like data loaders github.com/graphql/datalo…
X: ok, do you need them to build a product app?
me: no, you can absolutely build production apps without them, but these features can be very useful in some contexts, for example, Netflix uses federation heavily netflixtechblog.com/how-netflix-sc…
Read 7 tweets
I want to talk a bit about what this was like.
tl;dr: it was *long* and inconvenient timing but, as an operations team, not particularly stressful. Questions of “when”, not how or if systems would come back. A lot of waiting and watching—and that’s desirable.
Wednesday, there was not much to do. AWS IoT was hit hard by the Kinesis outage, which meant lots of stuff was simply not going to work. And CloudWatch outage meant we couldn’t see what was and wasn’t working cloud-side.
The resolution to the main outage came late in the evening. This meant we were up late because we needed to be there when we had visibility again into Lambda logs and DynamoDB metrics. If I had known that would be 6 hours later, I would have sent everyone to bed first.
Read 11 tweets
Some superb information from @matthew1000 on how the BBC is using cloud and #serverless: "Moving BBC Online to the cloud" medium.com/bbc-design-eng…
"The BBC website is huge. Over half the UK population use it every week. Tens of millions more use it around the world. It has content in 44 different languages. And it offers over 200 different types of page — from programmes and articles, to games and food recipes."
1) Don’t solve what’s been solved elsewhere - Around half of the BBC’s website is rendered serverlessly with AWS Lambda. Managing virtual machines (or containers) is expensive — keeping them secure, reliable and scalable takes time. Serverless mostly solves that problem for us.
Read 11 tweets
X : #Serverless seems quiet these days.
Me : Everyone is in the "too busy doing stuff" phase.
X : Lol, what's after?
Me : The old "oh my god, how big is this" phase.
X : And then?
Me : The rapid scramble by consultants to claim they've been doing it for ages.
X : Any advice?
Me : It's probably not a good time to write articles or publish papers saying #serverless is a flash in the pan or just for startups or not for enterprises.
X : Will people do that?
Me : Oh yes. They always do.
X : Other hints?
Me : Battle for serverless is pretty much over. In the West AWS won, MSFT 2nd, Goog 3rd and then a long drop off the cliff to everyone else.
X : Oracle?
Me : Good point. Three years after the battle has ended and everyone has gone home is when Oracle turns up ...
Read 4 tweets
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
What are some database engines that works great with serverless architecture?

#database #CodeNewbie #Serverless #javascript
Note to Self: MongoDB can be used with serverless functions by caching the initial connection.
database engines were designed much before the serverless architecture was a thing.

a connection to the database is always persistent. meaning, it lasts for a really long time.
also, there is a limit(imposed by DBaaS provider) on how many connections a database can have at any given timestamp.

a lambda function is invoked every time a client(generally, browsers) creates a connection. this means a new connection to the database as well.
Read 6 tweets
#OpenShift TV now live! OpenShift 4.6 What's New!
@openshift
Installer Provided Infrastructure for Bare Metal by @RamonAcedo
Read 66 tweets
Editing my conversation with @lajacobsson for @RealWorldSls and there's a nugget of insight that I wanted to share with you about implicit coupling that we often overlook when using SNS with SQS.

#serverless #aws

1/
The topic is usually owned by the publisher and deployed in the publisher's stack, and the subscriber would reference its ARN via a CloudFormation stack output or something, creating an implicit coupling there.

2/
You need message attributes to do filtering, but the publisher has no idea what the subscriber cares about (nor should it, loose coupling and all). So teams that own the subscriber have to ask the publisher's team to add the message attributes they need.

3/
Read 7 tweets
Launched a new app for client 3 weeks ago on AppSync, 5,000 users later, 100,000+ API calls per day, 99% cache hit rate, 0 problems, and 90% of AWS cost is on AppSync cache (T2.Small). Easily one of the most complex things I've ever built (in a few weeks). Gotta love #serverless!
Can't stress how liberating it is to NOT have to worry about capacity planning, tuning auto-scaling configurations and all that crap. Built everything on my own, working part-time, in a few weeks and it just works! Everything scales itself, and only pay for what we use.
Caching seems expensive right now, but is soaking up 99% of the load and it's gonna pay for itself 10 times over in a few weeks when we hit 10s of thousands users.

Oh, our Lambda cost is $0.00 (still within free tier) 😂 mostly direct AppSync to DynamoDB integration
Read 3 tweets
We're proud to publish our first State of Serverless report!
Thank you to our partners: @serverlessgurux, @snipcart, @triggermesh, @lvlupeng, @MeetupFeedio, @Cooperpress, @getiron, @Lumigo, @WebinyPlatform
#ServerlessSeptember #Serverless
Check it out: codingsans.com/blog/serverles…
Here's a collection of several key findings based on the community's answers:

1. Currently AWS @awscloud is the leading provider followed by @Azure and @GCPcloud
2. The two biggest benefits of using #Serverless architecture are flexibility in scaling and speed of development.
Read 7 tweets
We're giving away 5 copies of Carl's new book "Cloud Native Machine Learning" (thanks @ManningBooks 🙏)

If you wanna see how #serverless and #ML can beautifully complement each other, simply LIKE or RETWEET this tweet to qualify for the raffle.

There's still time to win a copy of Carl's new book "Cloud Native Machine Learning" and see how #serverless and #ML makes a perfect marriage, we'll announce the winners at noon on Friday GMT.

Good luck!
Congratulations 🎊 👏👏

@bexxmodd
@vattybear
@chongtingho
@hectoregm
@_ikhoa

Please DM me for your promo code so you can order your copy of Carl's new book! 💪
Read 3 tweets
Now LIVE: 🔥AWS Lambda Powertools for Java in Beta🔥

Easily trace your Lambda functions, and structure your Logs using annotations

HUGE thanks to @MarkSailes3 @PakPMO @SteveHouel for making this happen based on customer feedback

More details 👇

#serverless #aws #java
I wish I could edit Tweets now HAHA

Sorry @agrawalpankaj16 autocomplete made me choose Pakistan' Prime Minister!!!
Read 3 tweets
Please help us welcome our next curator Darryl Takudzwa Griffiths. @BlaqNinja completed his Bachelors Degree in Computer Engineering at DUT, graduated in 2011. Due to struggling to find suitable employment he went on to study multiple certificates from bodies such as Microsoft.
He has certificates in N+ (Computer Networking), A+ (Computer Technician & Technical Support), Certified Ethical Hacking V7 (CEH v7), Offensive Security Certified Professional (OSCP). Sadly even with these, he could not secure his desired post so in 2016 he moved to USA.
Darryl was able to secure a job in a corporation that owns casinos as a system analyst & security architect. Within the same year he embarked on a Masters degree in Robotics & Artificial Intelligence Engineering. In 2017 he resigned from his post and started his own company...
Read 99 tweets
something is coming...

#serverless #appsync #graphql Image
Teaser #1

✅ landing page
✅ sign-in page
✅ user registration with Cognito
✅ sign-in & sign-out
✅ Home screen

This is the demo app we'll be building. For now, you can see the registration & sign-in/sign-out in action.

More updates soon!

#serverless

Minor update - the website is up, and I'd love to hear your feedback on the curriculum.

Are there anything in particular that you'd like to learn? Am I missing anything glaringly obvious?

appsyncmasterclass.com
Read 6 tweets
I've gotten a lot of questions about "how do I become an AWS serverless hero?" or "what does being an AWS hero mean?" so I thought I'd share my thoughts here

#serverless #aws

1/
Firstly, it's NOT a programme that recognizes expertise, it's a programme that recognizes your contribution towards the community - i.e. it's not about what you know, but how much you empower others.

And no, you don't need to be certified, certs don't help AFAIK.

2/
It's a great recognition - I love it, and it has definitely helped my career progression. But it's still just icing on the cake. Empowering others is rewarding enough on its own and has defined my career, with or without the heroes programme.

3/
Read 7 tweets
⏰ What time is it? Time for a #Mythbusters thread -- #Serverless edition!

Agreed, the term is sub-par. But hear me out, the architecture is not. Let's talk about a few common misconceptions about Serverless!
1⃣ "Serverless means no servers"

There *are* servers involved, but it's not on you to run and operate them. Instead, the serverless provider is managing the platform, scaling things up (and down) as needed. Less things to take care of, billed per-use.

Myth: BUSTED!
2⃣ "Serverless is cheaper"

Pay-per-use makes low/medium-volume workloads really cheap. But pricing is complex: no. of requests, assigned RAM/CPU, API gateways, traffic etc. Depending on your workload (e.g. high, sustained), other options like VMs are better.

Myth: Kinda BUSTED!
Read 8 tweets
[Serverless Python Tip with SAM]

If you're trying to share code as well as common libraries across a few functions within your project - Check this out

You can use a local path to include requirements.txt, and additional local packages you want 👇

github.com/aws-samples/aw…
However, by only using Lambda Layers it'll break your autocompletion when developing locally incl. tests

For VS Code, you can extend PYTHONPATH by simply adding a `.env` file at the root of your project

👇 /2

github.com/aws-samples/aw…
As for your tests, you'll also have to include that path within your test runner (pytest:conftest.py) or add it programmatically via sys path like this

github.com/aws-samples/aw…
Read 5 tweets
phew, spend a good few hours re-organizing a sizable AppSync project (150+ resolvers, ~600 resources), found a nice way to split them in the end, think now we've got some more room to grow this project 💪 here's the before and after for comparison #serverless #aws #appsync ImageImage
unfortunately, the solution wasn't to just "add more nested stacks" because you also reach the 60 parameters limit because the no. of different Lambda functions & DynamoDB tables involved
in the end, I had to find a way to slice along the data sources and pull everything up (DynamoDB tables/Lambda functions/log groups/IAM roles) and down (resolvers, function configurations, IAM roles) together
Read 5 tweets
Done more performance analysis of the new Lambda-EFS feat. Some interesting findings, longer write-up to follow.

1st: mounting an EFS volume has no impact on Cold Start duration (as measured by InitDuration)

2nd: it is much FASTER and more predictable than S3

#serverless

/1
On the initDuration, on a relatively small sample set (~100) I didn't detect any noticeable difference between the control and EFS ("efs-test") functions.

/2
For read/write performance, it's clear to see that EFS is both faster and more predictable (i.e. lower SD) compared reading & writing from/to S3.

But something was weird - notice those big "jumps" between the tail latencies for EFS read latencies?

/3
Read 7 tweets
🔥 AWS Lambda Powertools for Python is now GA 🔥

We're now GA with four utilities

🌟Core: Tracer, Logger, and Metrics
🌟Bring your own middleware

Core contributors: @Tom_McC @NMoutschen

More details in this 🧵

#serverless #aws #python
github.com/awslabs/aws-la…
Last year I was fortunate enough to speak at re:Invent about Serverless Architectural Patterns and Best Practices

That preceded the work we've been doing with the AWS Well-Architected Serverless Lens since 201, however there was to it than patterns..

At the end of the session, after lots of water, if you watched ;), I talked briefly that Patterns are important to understand what worked well but we shouldn't hang to it as the ultimate truth

That was the hook for the Serverless Lens that came later

aws.amazon.com/blogs/aws/new-…
Read 11 tweets
I have spent quite a bit of time with AppSync on a few projects, and it's really grown on me, big time. So much of what's difficult with API GW comes out-of-the-box.

Here are 5 things that really stood out (a long form blog post to follow soonish)

#serverless #aws #graphql

1/
1. Coginot group-based authentication.

This is a big undertaking with API GW, you have to assign IAM roles to groups, set precedence order, then write a custom auth Lambda func & generate policy yourself.

With AppSync, it's built-in, literally a one-liner!

2/
2. Request & response validation.

With API GW you need to set request model (not bad) but there's no response validation (the response model is only used for doc generation) so you have to roll your own.

With AppSync, it's just how GraphQL works, no extra work required.

3/
Read 11 tweets
A really good Q during the last Q&A session of my Production-Ready Serverless workshop. Thought I'd share it here.

Q: "I have a nightly task that load some data from RDS and then write it to S3, should I have 2 functions for this with API between them?"

#serverless #aws

1/14
I always start from the simplest solution and go up from there, and stop at the least complicated solution that meets all my criteria.

In this case, if everything can be done within the 15 mins limit, I see no reason to split the functions.

Follow the KISS principle.

2/
But, there are many reasons to split the steps into multiple functions.

E.g. to increase parallelism, you may split the task up into many small tasks, and fire off an invocation (separate function) to handle each.

Which means you need some sort of queue, but which?

3/
Read 14 tweets
So if you're watching the #Serverless-First Function you might have just seen this slide on measuring and comparing #security between a serverless app and a "Monstrous Monolith."

Did you know there are actually numbers you can calculate and measure? 1/
Take another look at this formula from two slides previous:

Let's break down each of this components. 2/
c = each function's computational complexity

This is essential or irreducible complexity as defined by T.J. McCabe all the way back in 1976. It's a positive integer, and you can calculate it. 3/

ieeexplore.ieee.org/document/17023…
Read 8 tweets

Related hashtags

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.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!