Slack uses a job queue system for business logic that is too time-consuming to run in the context of a web request. This system is a critical component of their architecture, used for every Slack message post, push notification, URL unfurl, calendar reminder, and billing calculation.
Your application is serving requests constantly for your users. You and your team want to ship features and fixes as soon as they are ready, so you do continuous delivery. But what happens to your users who used your product at the time of the deployment? Chances are, the requests they have in progress are going to fail. This post helps you fix that.
It’s hard to make money as an open source software developer. There are options, but they have a lot of downsides.
You can work for a big company that can afford to let you do work that doesn’t directly relate to its products. But sometimes it’s hard to balance the work you’re not passionate about with the work that you are. You shouldn’t work for someone that you don’t want to work for — it’s a lose-lose.