Zendesk Engineering
medium.com/zendesk-engineering · Company blog · on HN since 2016
Zendesk's engineering team writes about its production systems, including Go, Ruby and Kafka, TensorFlow serving, GraphQL tooling, and logging.
What HN saysHN commenters link it mainly as an example of Zendesk's engineering work, such as the SimpleDB post; no strong opinions appear in the given comments.
18HN people shared it
2linked it in comments
22stories submitted
214story points
1 year agolast shared
2016people per year2026
Most-shared posts
- 1Hunting down a C memory leak in a Go program2 people · 146 points · first shared 2021 · 46 comments on HN
- 2Racecar: a simple framework for writing Kafka consumers in Ruby2 people · 9 points · first shared 2017 · discussion on HN
- 3How Zendesk Serves TensorFlow Models in Production2 people · 7 points · first shared 2017 · discussion on HN
- 4Datadog Log Management from Zero to One2 people · 2 points · first shared 2019 · discussion on HN
- 5Open sourcing node-publisher1 people · 16 points · first shared 2018 · 4 comments on HN
- 6Laika – Test, Mock, Record and Replay GraphQL Operations in Apollo Client1 people · 16 points · first shared 2021 · discussion on HN
- 7Zendesk’s Global Mesh Network- Part 11 people · 3 points · first shared 2019 · discussion on HN
- 8The history of infrastructure at Zendesk (Part 2) – the messy middle1 people · 2 points · first shared 2019 · discussion on HN
- 9The Dawn of Zendesk’s Machine Learning Model Building Platform with AWS Batch1 people · 2 points · first shared 2018 · discussion on HN
- 10We Need to Stop Being Short Sighted and Start Hiring Junior Software Engineers Now1 people · 2 points · first shared 2017 · discussion on HN
- 11How probable are collisions with ULID’s monotonic option?1 people · 2 points · first shared 2020 · discussion on HN
- 12Improving Gender Diversity in Engineering – Zendesk Engineering – Medium1 people · 2 points · first shared 2018 · discussion on HN
- 13Hunting for Memory Leaks in Python Applications – Zendesk Engineering – Medium1 people · 1 points · first shared 2019 · discussion on HN
- 14How we improved the observability of a Go project – Zendesk Engineering1 people · 1 points · first shared 2018 · discussion on HN
- 15Debugging on Customers’ Websites1 people · 1 points · first shared 2016 · discussion on HN
What HN people wrote when they linked it
rudi-c · 2019-08-22
(Author here)
There is material on the internet that are relevant to the topic, but it's quite hard to piece together. After all, there are only a handful of players right now who need to build an API that isn't a REST API.
Among big names, I can think of Zendesk (uses iframes), Coda (runs third-party code on their servers IIRC, isolated via server mechanisms), Salesforce (not sure exactly what they do, but I think they also use Realms as a component to their system).
https://medium.com/zendesk-engineering/sandboxing-javascript-e4def55e8…
https://trailhead.salesforce.com/en/content/learn/modules/lex_dev_lc_v…
There's a couple of academic papers on JavaScript isolation, but you'll have to do a lot of work to figure out how relevant they are. Be sure to check the publication date.
The folks at Agoric are probably the leading experts actively working on untrusted code isolation in a browser environment right now. I would follow them if you want to hear about the latest new tech: https://github.com/Agoric/SES
otterley · 2020-11-22