Learn how our team built a proactive defense mechanism to automatically identify threat behaviors and respond in real-time.
Instead of waiting days or hours for human intervention, the Anomaly Event Response responds in minutes.
slack.engineering/building-s…
Slack Engineering retweeted
How I felt in love with Slack and eventually got a job there. A story of overcoming failure and chasing your dreams. Featuring @jewelia @rands @iamcal @dustyp @krismerrill @tvars and my own family. turelin.medium.com/how-i-fel…
Slack Engineering retweeted
What happens when your distributed service has challenges with stampeding herds of internal requests?
How do you prevent cascading failures between services?
We share how circuit breakers helped prevent internal cascading failures at @slackeng @SlackHQ!
bit.ly/cicd_cb
In case you missed it: Learn how @SlackHQ uses product thinking to improve our internal tools slack.engineering/applying-p…
Slack Engineering retweeted
a new research paper by Slack engineering outlines a #metrics storage engine that's better than @PrometheusIO. Check out OpenObservability Talks with @mansu to hear about it:
youtu.be/IvidkV3TfYg?t=919
or on the podcast apps:
ow.ly/3h6A50I5b6X
@SlackEng @OpenObserv #devops
Slack Engineering retweeted
🎉 @Carlos_vr_ and I share how @slackeng evolved socio-technical workflows to increase developer velocity and to redefine confident testing and deploy workflows.
bit.ly/3LNtm0S
1/
Slack Engineering retweeted
What does it take to build #observability in web-scale company such as @SlackHQ, @Pinterest & @Twitter?
Tune in to OpenObservability Talks @OpenObserv to hear it first hand from @mansu
@SlackEng @TwitterEng @PinterestEng
Live-streaming 16 Feb, 11 AM PST
youtu.be/IvidkV3TfYg
“Building the Next Evolution of Cloud Networks at Slack: A Retrospective” from @SlackEng slack.engineering/building-t…
Slack Engineering retweeted
🎉 slack.engineering/infrastruc…
A deep dive on how we crafted an order of magnitude change in our spend (10x reduction compared to baseline growth) over the last two years with iterative understanding and changes in Slack’s Continuous Integration (CI) infrastructure. 1/
Slack Engineering retweeted
"The Four Agile Values and Slack" by Ashoke Chakrabarti @brianriggsbee Elizabeth Beddiaf. A great article by @slackeng! lnkd.in/ggn8AU8h
A well-designed API can boost developer innovation, while a poorly designed one can be a liability.
@episod and @saurabhsahni provide an inside look at our API design principles with some ideas that you can take back to your own process. slack.engineering/how-we-des…
Slack Engineering retweeted
Curious to learn how @SlackEng implements Role Management & Authorization and missed yesterday's @TwitterSpaces chat with @jakebyman and Aish Dahal?
Don't worry! Got you covered 🎉youtube.com/watch?v=-iVBsaga…
Slack Engineering retweeted
1/ In the 2nd Authorization @TwitterSpaces chat
we'll learn how @SlackHQ designed, implemented and rolled out a big change at scale: their new authorization features
On Wed at 4:30 PM PDT I'll chat with @jakebyman & Aish Dahal, two @SlackHQEng engineers who worked on this
A decent number of Slack's features were once ideas and prototypes at our internal hackathon.
We've been running hackathons since 2016, learned a few things along the way, and wrote up 9 tips for throwing a successful (and fun!) one: slack.com/blog/collaboration…
Performance problems can be a real struggle to track down, especially if they're hard to reproduce.
We're using distributed tracing to understand work that spans multiple services and the client. Our colleague Justin wrote up how we're actually doing it: slack.engineering/client-tra…
That high school student was @_clavin, now one of our @electronjs engineers!
A high school student was submitting great PR’s to Slack’s open source projects. That turned into an internship and now, a full time job. stackoverflow.blog/2021/03/2…
Slack Engineering retweeted
“Migrating Millions of Concurrent Websockets to @EnvoyProxy” via @SlackEng slack.engineering/migrating-…
January 4th was the first working day of 2021 for many people. As the sun rose in the Americas, so did our internal error rates.
Every incident is an opportunity to learn, and an unplanned investment in future reliability. Here's what we learned: slack.engineering/slacks-out…
