Profile picture
Simon Wardley @swardley
, 3 tweets, 1 min read Read on Twitter
People keep asking ...
1) serverless first, on a public provider. Don't rebuild services that already exist, consume them.
2) If you must, then use containers sparingly on a public provider. Remember containers are less constrained and flexibility is not a friend.
If you're told that you need to build on-premise then stop, robustly challenge the idea, question why is this, ask if anyone has actually used serverless and explain you'll consider a proposal whilst cutting IT spending, reducing headcount and sweating existing assets.
X : Why reduce headcount or sweat existing assets?
Me : Removal of inertia. Make sure the axe falls on those wedded to past practice. Serverless isn't a question of "if" but "when" and whilst you should give people a path (i.e. investment in education), inertia must be managed.
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 Simon Wardley
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!

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!