With news of Meta aiming to flatten their management chain, I talked with engineers and managers at the company on their thoughts. An engineer shared how it feels reporting chains in some orgs are out of hand. The ones below are actual chains for some outlier IC positions:
Sure, you're not Spotify, Google, Amazon, or Netflix. You're you, with your own unique organizational challenges.
It doesn't mean we can't learn from the big companies. In this @InfoQ talk, Travis from Netflix explains how they scale authorization.
https://t.co/kQTgN2xQQX
How do we design a system using the 𝐞𝐯𝐞���𝐭 𝐬𝐨𝐮𝐫𝐜𝐢𝐧𝐠 paradigm? How is it different from normal system design? What are the benefits? We will talk about it in this post.
Evolution of the Netflix API architecture.
The Netflix API architecture went through 4 main stages.
𝐌𝐨𝐧𝐨𝐥𝐢𝐭𝐡. The application is packaged and deployed as a monolith, such as a single Java WAR file, Rails app, etc. Most startups begin with a monolith architecture.
How to scale a website to support millions of users? We will explain this step-by-step.
The diagram below illustrates the evolution of a simplified eCommerce website. It goes from a monolithic design on one single server, to a service-oriented/microservice architecture.
"Platform Engineering" is rapidly becoming the new DevOps or SRE. Almost every day we hear about another org building an internal developer platform or control plane.
Want to know what platform engineering is, where the trends are going, and why you should care?
Read on 🧵👇
Following on from sharing how we sparked the creation of a Data Office within the LEGO Group, we've just published the next article on how we're approaching the challenge of Maturing a Data Literacy Initiative in a Large Organization https://t.co/GspmbEirll
In distributed systems, especially deep SoA and microservice architectures, retries are mostly bad, despite being considered by many to be a "best practice". Specifically, doing more when when you're overloaded is bad for availability, stability, and efficiency.