Discover and read the best of Twitter Threads about #cloudnativelondon

Most recents (4)

Final keynote of #CloudNativeLondon is @sarahjwells on how we have to change our organizations when our systems become complex & distributed cloud-native systems (and what to check _before_ you build a cloud-native system)!
@sarahjwells Only go cloud-native if you have a business reason.

In the case of the FT, it's because subscriptions on their website became an existential source of revenue.

Experiments are only experiments if you can do them at low cost. FT does 100s of A/B tests/year. #CloudNativeLondon
and that means releasing upon demand 2000x a year, using cloud-native architecture.

But there was a cost to the switch. "there's complexity around the edges." things can go wrong. #CloudNativeLondon
Read 35 tweets
.@DataShedStew on operating (a non-profit for banning oneself from gambling): scale to handle 20k QPS at peak in less than 300ms per request... because they are in the critical path of _every_ request in the UK gambling industry. #CloudNativeLondon
@DataShedStew and he's onboard with the philosophy of "yes, it should be safe to release on Fridays!" (by having continual, well-managed change, instead of trying to preserve inertia) #CloudNativeLondon
He argues that if an error in your service can result in someone potentially relapsing on a gambling addiction, it is worth the money to scale up by hand in advance (costing additional $$$) rather than tolerating dropped requests during default autoscaling. #CloudNativeLondon
Read 4 tweets
Next up at #CloudNativeLondon is my friend @ellenkorbes on modern k8s tooling!
@ellenkorbes This talk is for developers working on apps that run on k8s and are not k8s itself. #CloudNativeLondon
You shouldn't have to think about k8s internals as a developer, similar to how you shouldn't have to be a plumber to use a faucet. #CloudNativeLondon
Read 18 tweets
Excited to be livetweeting @jezhumble's brand new talk on DevOps and Cloud Native at #CloudNativeLondon!
@jezhumble Netflix did the shift from traditional ops to "NoOps" which... didn't actually remove the need for ops, just ops as a separate department. #CloudNativeLondon
but what it did highlight was that instead of having ops departments, we have started having _platform_ engineering departments separate from product dev teams. #CloudNativeLondon
Read 37 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!