This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
So small changes were submitted, reviewed, and integrated into the live code base as quickly as possible. The earliest technical problems centered on how to store all that data, and then how to search it. What current – and future – technologies can we use to lower their costs? What causes friction in the customer experience?
In March I wrote the following: Observability is a paradigm on which we can build a safe, healthy, sustainable future for the tech industry. A better tech industry is better for supporting this complex, interdependent society we live in. Though our deploy velocity remained the same, the engineering org has been far from stagnant.
But did you know that a big chunk of Netlify’s engineering team is in the backend? These fine folks architect the scalable build system workflows, edge routing, telemetry, metrics, account management, lambda functions, and so much more that everything depends on. I get to work with really smart people who push me to grow.
In March I wrote the following: Observability is a paradigm on which we can build a safe, healthy, sustainable future for the tech industry. A better tech industry is better for supporting this complex, interdependent society we live in. Though our deploy velocity remained the same, the engineering org has been far from stagnant.
If you look at chaos engineering, like.1 Our Chaos Monkey was like a Python script in AWS Lambda. This still technically runs but it’s on its way out. There’s just a lot of lack of diligence, is what I’d call it, in our services. They would come through, kill some nodes. Don’t jump into it.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content