me/acaloiaro.github.io
1
0
Fork 0
mirror of https://github.com/acaloiaro/acaloiaro.github.io synced 2026-07-21 18:29:18 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated indecision wording

Browse source
This commit is contained in:
Adriano 2018-07-03 20:24:52 -04:00
parent a6b816fac6
commit 6318e37441
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
_posts/2018-07-03-slaying-the-monolith.md
View file

@ -71,6 +71,6 @@ A status change channel to convey changes in worker status to listeners: e.g. mi
A monitor goroutine that waits for events on the status change channel and takes action. The most common action is restarting workers that are in a bad state.
Most importantly, what this process barrier gives us is the critical ability to kill unhealthy LibreOffice workers and assign deadlines to RPC calls. In short, it’s what prevents a single bad document conversion from dragging the entire system down with it, allowing us to scale from tens of documents per day to tens of thousands.
If we built this on our Rails monolith, we would have been in for a world of hurt. What would have happened had our production application been directly exposed to runaway LibreOffice processes? What would the development and debugging lifecycle look like had this been done inside of a Sidekiq worker? Would our infrastructure and security teams be comfortable shipping LibreOffice in the monolith Docker image? I feel bogged down in indecision even asking these questions hypothetically. I’d rather be building things and making real progress.
If we built this on our Rails monolith, we would have been in for a world of hurt. What would have happened had our production application been directly exposed to runaway LibreOffice processes? What would the development and debugging lifecycle look like had this been done inside of a Sidekiq worker? Would our infrastructure and security teams be comfortable shipping LibreOffice in the monolith Docker image? I feel crippled by indecision even asking these questions hypothetically. I’d rather be building things and making real progress.
Interested in working on projects like Dochouse that impact thousands of users every day? [Greenhouse is hiring](https://grnh.se/716d31af1) Software Engineers. Join us!