Discover and read the best of Twitter Threads about #serverless

Most recents (24)

Now @rchrdbyd takes the #serverlessconf stage.

It turns out that "Date a Scientist" isn't the term and my startup gained no traction.
I see @rchrdbyd is collecting stamps for his programming language passport. #Serverless
c4 instances are thusly named because they'll blow up in your face and take a building down. #Serverlessconf
Read 11 tweets
Love the simplicity of #Serverless #FaaS (Function-as-a-Service) but hate the setup process? Look to these 7 open source projects to ease #AWS Lambda deployments:
#BigData #StreamingAnalytics #Cloud #DataScience #MachineLearning #IFTTT #EventDriven #AI
13 free tools for #API design, development, & testing — for example, Amazon API Gateway allows you to build front-end APIs for applications built on Amazon EC2, #AWS Lambda, or any web application:
#microservices #cloud #serverless #FaaS #coding #IoT
#IFTTT alternatives for developers of #EventDriven workflows:
#IoT #EdgeAnalytics #EdgeComputing #Microservices #DataScience #BigData #FaaS #ML
+See the book “AWS Lambda in Action: Event-driven #Serverless Applications” at
Read 4 tweets
Every programming language which has gRPC server support is a possible user language for @CloudstateIO #serverless
@CloudstateIO Every service exposed via a @CloudstateIO proxy is reachable *both* via #gRPC and HTTP+JSON—for optimal performance and optimal interoperability.
@CloudstateIO Every service exposed via a @CloudstateIO proxy can be explored via #gRPC Server Reflection. This means that all tooling which understands Server Reflection can be used, such as grpc-cli.
Read 6 tweets
Following the news around a certain large tech company's conference this week and their numerous k8s announcements furthers my view that #serverless is the future of things. 1/
And by #serverless i mean highly abstracted, almost entirely managed, cloud-based services. I'll give you Fargate, but not lower down the stack from that 2/
I've said for a while now that k8s is the last hill for traditional Ops/IT to die on. above that on the stack is basically all things serverless. So every traditional IT vendor in the world catering to this is their deathknell as well. They become bottled into this dead end 3/
Read 12 tweets
(1/4) On #cloud technology and #climatechange...the narrative around cloud is about business agility and modernization. That's fine, let's do that. A more compelling reason is to reduce the power consumption of all those corp data centers.
(2/4) We are in a #climatecrisis. Crisis means, extraordinary action is needed. IT professionals have three responsibilities because business as usual does not cut it.
(3/4) 1.) Advocate for/demand that cloud providers use renewables 2.) Advocate for the use of cloud solutions 3.) Re-imagine your tech stack using #serverless
Read 4 tweets
In addition to #serverless (see link), my other new favorite piece of hashtag-compliant vocabulary for Pantheon is #WebOps

Let me explain.

The default short-hand for what we do is, of course, "hosting." The dreaded H-word. It's part of our story for sure, but it misses out on the value Pantheon provides.

It's an incomplete "what" that thoroughly misses out on the "why."
Don't get me wrong. Hosting is super important, and if your hosting setup is bad or broken, it's really hard to see past it.

A burning platform is an all-consuming emergency. If that's your situation you should call us; we can help!
Read 15 tweets
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.
Read 3 tweets
Sipping my *oat milk latte* #ClimateCrisis…

(also... Bustle is #serverless so it's on-demand compute is likely more environmentally friendly too…)

#ClimateCrisis #nailedIt
One thing though, personal changes aren't going to make a big difference. Systemic and governmental changes are.

Big system change?

If you work in tech, Sustainable Servers - Data Centres are as bad as aviation for carbon emissions…
Switch your servers to a provider that uses renewable (or at least sustainable) energy

GCP: Almost all renewables, and offsets the rest
Azure: 60% renewables and offsets the rest
AWS regions: Ireland, Frankfurt, Montreal and Oregon are "sustainable"
Read 3 tweets
I've been spending a lot of time lately with @dynamodb in my #serverless applications, so I thought I'd share my surefire guide to migrating to it from #RDBMS. So here is…

How to switch from RDBMS to #DynamoDB in *20* easy steps… (a thread)
STEP 1: Accept the fact that can fit 90% of their retail site/system’s workloads into DynamoDB, so you probably can too. 🤔
STEP 2: Create an Entity-Relationship Model, just like you would if you were designing a traditional relational database. 👩‍💻
Read 23 tweets
Listening to @johnbdickson at #RMISC - AppSec in a World of Digital Transformation
@johnbdickson Businesses are demanding speed in software development over and above nearly every other requirement. This can be an opportunity for AppSec teams – @johnbdickson at #RMISC #RMISC2019
"Digital Transformation" is a business-oriented term, and as such it's a little ill-defined. It's basically code for "we don't want to get stomped by people like Netflix who are moving fast" – @johnbdickson at #RMISC #RMISC2019
Read 17 tweets
The serverless shift

* From Code to Configuration
* From High LoC towards Low LoC (preferably zero)
* From Building Services to Consuming Services
* From Owning Workloads to Disowning Workloads
From Code to Configuration

Configuration is a form of "code", but is not necessarily programming. It defines the resources and services used and how they are combined for an application. The code is the ***unique business logic*** required for the application.
From High LoC to Low LoC (preferably zero)

Today's code is tomorrow's technical debt. Code is always a liability at some point in the future. Limiting this future liability is a good thing. Working to reduce this liability from the beginning is simply good practice.
Read 6 tweets
What? You mean... you mean... that software lives on beyond the deployment? Beyond the first few minutes/hours/days? Until you retire it? #sarcasm

I think we need a new phrase:

"Your code is for life, not just for deployment"

cf "A dog is for life, not just for Christmas"
I love @mipsytipsy talking truth. She's one of the few who simply nails it almost every time.

Too many devs fail to think about the effects of their code over any term other than the deployment and a bit after.

Maybe because their salary doesn't depend on quality over time?
If devs were paid a bonus based upon the amount of technical debt they created - the less they created, the better their bonus - would the world be a better place?

Because maybe that should be a thing we consider.
Read 11 tweets
"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
Watching a talk on event drive architectures at #qconlondon #qcon. Interested simply to find out exactly how much #serverless simplifies everything.
Talking about Dash Buttons and how to work with them. Talking about decoupling services when a button is pressed. I think it's going to go down the road of explaining an event driven approach...
It's interesting to note that the speaker is talking about "services" that are created... in my mind, most of these things are incredibly simple Lambda functions.
Read 35 tweets
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
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
I'll be live-tweeting in an hour as members of the AWS #Serverless Apps Repo team demo the apps they've built this week during the #sarhackathon 🐿
First up is lambda-versions-deleter…. This app will clean up your old Lambda Function Versions for you. Inspiration came from a pain-point we experienced internally while building Serverless Apps Repo.
Next we have cw-logs-to-chime…. This app listens to CloudWatch Logs and sends them to a Chime ( room. Be sure to specify the FilterPattern parameter!
Read 13 tweets
I haven't written many blog posts recently. There's a reason: I'm in a reorientation phase in a strategic/business sense. I'm doing a lot of chatting with people in the #serverless community though. I've been working on a startup that I have mostly shelved (way too early).
I've worked on too many startups in my 20+ career to waste my time on something without having a certain amount of clarity around the product and the business model. Sometimes you can get away with it, but the current #serverless market is not mature enough for this startup.
So, I'm talking with a few trusted people and looking at doing a bit of p/t or interim CTO work for the foreseeable whilst I figure out next steps - if you'd like me to come and do some consulting/training/mentoring, please DM me (they're open).
Read 3 tweets
#prod365 #fr Les Plans de Continuité d'Activité (#PCA) ont pour but de retablir le SI après un "désastre". Un tel événement est aussi appelé "Disaster Recovery" (#DR) et inclus de nombreux événements graves, notamment la perte de #datacenter ou de données.
Citons quelques exemples: corruption silencieuse, destruction du medium de stockage (par erreur ou par nuisance: piratage ou rogue employee), isolation réseau (coup de pelleteuse dans la fibre), script d'administration mal fait / boucle foireuse, clause WHERE oubliée...
Pour de multiples raisons, certaines applications ne peuvent pas être disponibles en Actif/Actif, seulement Actif/Passif.
Cela implique de pouvoir répliquer les données live et de les réutiliser sur une autre machine.
Read 10 tweets
2019 Wish : The #serverless community practices what it preaches, and focuses the conferences/talks/articles on the value gained, rather than the technology and concepts. In fact, we probably need to have some basic rules for serverless content. For example -
1) Must identify yourself as a practitioner (someone leveraging #serverless technologies to build something of end customer value) or a provider (someone who is providing technology that elables a practitioner to go serverless).
2) Practitioner content must highlight the agility/elasticity/cost gains from using the serverless tech, and the business value tied to solution.Bonus points for minimal code written:: value ratio.
Read 8 tweets
#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
Past few days the serverless hot takes I’ve seen are:

- serverless without containers!
- infra provisioning is hard so we need serverless.

They’re just distractions. 1/*
1 - How my serverless platform works is largely irrelevant to me. That’s the point. What matters to me is what the platform provides.
2 - Don’t confuse individual developer problems with organization problems. How many organizations are making devs configure their own infrastructure?
Read 9 tweets
Coming up on the 4 year anniversary of the preview announcement of #AWSLambda here at @awscloud and put together this small snapshot of what the team has delivered over the past 4 years. tl;dr: its a lot. #serverless
2/ this works out to a release per month over the past 4 years and we're not even done with 2018 yet. it doesn't include region launches (in every public region)
3/ It also doesn't include what isn't seen to customers, all the internal bits, scaling, operational work, performance improvements, security related work, automation, refactoring, etc, that goes on probably a factor or two greater than this here
Read 6 tweets
I did a lot of work on outcome (worth based) models back in 2004-2007 ... they tend to expose weakness in the business to define value and inability of budgets to cope with variable models -…
One of the most interesting aspects of Serverless - as we move to measuring capital flow and opex for running code, as IT becomes even more an enabler rather than an obstacle - is the shift will expose huge weaknesses in other groups (from strategy to finance to HR) ...
... in the past, IT has always been the whipping boy, the one to blame, to point the finger at. In reality, past inefficiency & ineffectivess in IT has simply masked wider organisational problems. The next decade should get very interesting ...
Read 5 tweets

Related hashtags

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!