Sidekiq と Solid Queue の機能比較 - Kaigi on Rails day2 Sidekiq vs Solid Queue によせて - Techouse Developers Blog
Kaigi on Rails 2024 に参加しました こんにちは、クラウドハウス採用でエンジニアインターンをしている Higashiji です。 10 月の 25・26 日、Ruby on Rails についてのカンファレンス、 Kaigi on Rails 2024 が開催されました。 弊社からは新卒エンジニアの @izumitomo が「デプロイを任されたので、教わった通りにデプロイしたら障害になった件 ～俺のやらかしを越えてゆけ～ 」というセッションで登壇しました。 スライドがアップロードされているので、興味を持っていただけた方はぜひご覧になってください。 私はこれまでカンファレンスに参加したことがなかったのですが、カンファレンス参加費補助制度を使って初めて参加させていただきました。 本記事では、Shinichi Maeshima (@willnet) さんによるセッション Sid
sidekiq + redisの構築(Rails 4系) 4-1 - kikeda1104's blog
インフラの準備を分割して書いていきます。 前提環境: ElasticCache(Redis 4) AWS EC2(Amazon linux) AWS(Amazon Linux) 東京リュージョン 検証環境として、立てていきます。(EC2はのぞく) EC2 EC2は立てている前提で、サーバにsshで接続して、redis(client)とmonitをインストール # ssh -i ~/.ssh/[秘密鍵] ec2-user@example.co.jp $ sudo yum install -y monit $ sudo rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm $ sudo yum --enablerepo=remi install redis ElasticCache(Redis 4) 費用面を抑
Blue-Green deployments for Sidekiq workers in docker
It’s quite common nowadays to do blue-green deployments. The way they work is quite straightforward. Whenever you need to deploy a new version of your code to production, you go through the following steps: A new version of your production infrastructure is created, with the new code in it, while the old version remains untouched.Once the new infrastructure is up and running, some process checks i
Reducing Sidekiq Memory Usage with Jemalloc | Brandon Hilkert
Ruby and Rails don’t have a reputation of being memory-friendly. This comes with a trade-off of being a higher level language that tends to be more developer-friendly. For me, it works. I’m content knowing I might have to pay more to scale a large application knowing I can write it in a language I enjoy. Turns out…Ruby’s not the memory hog I’d previously thought. After some research and experiment
Incrementally moving to Elixir
Like many working in a legacy Ruby system and learning Elixir we were struggling to figure out how to start moving our code over. Here I wanted to share a technique we used a year ago to start the process. BackgroundAt Fitzdares (a bookmakers) we have an ageing monolith of a system written in Rails over 7 or so years by various teams and contractors and much like the building above it’s starting t
Running Sidekiq On Heroku Free Dyno With Puma
In my opinion, Heroku is the nearly perfect place to deploy a project. It provides support for a lot of technologies out of the box with minimal or no configuration. Similarly, Sidekiq is what I strongly prefer whenever there is a need for background job processing. It ships with all the right set of APIs to deal with background processing and more importantly a great monitoring dashboard. So, Las
Graceful shutdown of Sidekiq processes on Kubernetes
In our last blog, we explained how to handlerolling deployments of Rails applications with no downtime. In this article we will walk you throughhow to handle graceful shutdown of processes in Kubernetes. This post assumes that you have basic understanding ofKubernetesterms likepodsanddeployments. ProblemWhen we deploy Rails applications on kubernetesit stops existing pods and spins up new ones.Whe
Ruby用バックグラウンドジョブライブラリ「sidekiq」のコードを読んでみる（前半） – なまけものからの脱却を目指すITエンジニアのメモ
自分が担当するRailsアプリケーションでバックグラウンドジョブを動かす必要が出てきた。 Railsでバックグラウンドジョブといえば二大巨頭の Resque と Sidekiq があると思っている。どちらかといえば最近採用されているイメージがあるSidekiqに関して、どんなコードになっているか主要な部分をチェックしておきたい。 今回は、Railsにsidekiqを組み込んでジョブを登録する部分まで。Sidekiqを直接使ってジョブを登録する方法と、ActiveJob経由で登録する方法の2つを比べて見る。 まとめ Sidekiqを直接使用する場合、Redisのコネクションプールを用意しておき、それを使用して各Jobの情報をキューにpushしているだけ。ジョブの登録に関してはシンプルだった。 ActiveJob経由もバックエンドを抽象化している分、少しコードが複雑になっているが、やっているこ
Kubernetes: (Graceful) Sidekiq Worker Lifecycle
IntroductionWith our recent release of Container Stacks v2 into public beta we're totally loving Kubernetes. But as with all love affairs, there are some bothersome aspects that we have to accept and work with. One such aspect is in the inflexibility of the vanilla shutdown sequence provided by Kubernetes. We're also prolific users of Sidekiq for the parts of our backend that are ruby-based (we're
What I learnt today from reading gems' code
What I learnt today from reading gems’ code Today I was working on chillout.io client and while I was debugging some parts, I had a look at some Ruby gems. This is always an interesting experience because you can learn how other developers design their API and how different it can be from your approach. Sidekiq So here are some interesting bits from sidekiq code. Sidekiq::Client initializer module
Hello Sidekiq 5.0
2017-04-25 After a few months of work, I’m happy to announce that Sidekiq 5.0 is now available. Sidekiq 5.0 refactors the core job processor to work better with Rails 5 and includes a few breaking changes that have been pending for a while. What’s New? Rails 5 native! Sidekiq::Processor has been redesigned to work well with Rails 5.0’s Executor. The Executor is a new API which needs to wrap any us
Instrumenting Sidekiq | Getaround Tech
Instrumenting Sidekiq April 20, 2017 – Michael Bensoussan – 7-minute read This article was written before Drivy was acquired by Getaround, and became Getaround EU. Some references to Drivy may therefore remain in the post As Drivy continues to grow, we were interested in having more insights on the performance of our jobs, their success rate and the congestion of our queues. This would help us: Be
Monitoring Sidekiq using AWS Lambda and CloudWatch | Brandon Hilkert
A few articles ago, I wrote about how to monitor Sidekiq retries using AWS Lambda. Retries are often the first indication of an issue if your application does a lot of background work. As Bark continues to grow, we became interested in how the number of jobs enqueued and retrying trended over time. Using AWS Lambda to post this data to CloudWatch, we were able to visualize this data over time. The
GitHub - jrallison/go-workers: Sidekiq compatible background workers in golang
package main import ( "github.com/jrallison/go-workers" ) func myJob(message *workers.Msg) { // do something with your message // message.Jid() // message.Args() is a wrapper around go-simplejson (http://godoc.org/github.com/bitly/go-simplejson) } type myMiddleware struct{} func (r *myMiddleware) Call(queue string, message *workers.Msg, next func() bool) (acknowledge bool) { // do something before
Introducing our Sidekiq cluster script
Introducing our Sidekiq cluster script By Benjamin Curtis on Feb 8, 2017 At Honeybadger we depend heavily on Sidekiq in our processing pipeline. Nearly everything we do runs through a queue at some point. As a result, I want to make sure we are running Sidekiq well. With our recent move to EC2, we changed from having a stable set of long-lived servers to an ever-changing set of instances running o
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
デプロイを任されたので、教わった通りにデプロイしたら障害になった件 ～俺のやらかしを越えてゆけ～
GitHub - mhenrixon/sidekiq-unique-jobs: Prevents duplicate Sidekiq jobs
和訳：sidekiq-shceduler README - Qiita
Signals
Sidekiq won't start when using Sidetiq ERROR: Actor crashed! · Issue #650 · celluloid/celluloid