--- description: IronMQを実際に使用したユーザーのレビューから、製品の機能や価格、メリットデメリットをご覧いただけます。類似製品との比較も簡単、ぴったりのSaaSが見つかるはず！ image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: IronMQとは？ | 機能や料金、導入事例をご紹介【キャプテラ】 --- 現在地表示: [ホーム](/) > [アプリ開発ツール](/directory/30082/application-development/software) > [IronMQ](/software/182241/ironmq) # IronMQ Canonical: https://www.capterra.jp/software/182241/ironmq ページ：1 / 2\ 次へ: [次ページ](https://www.capterra.jp/software/182241/ironmq?page=2) > 高いスケーラビリティと柔軟なメッセージ・キュー機能を備えています。柔軟なデプロイメントが可能で、極めて高速で堅牢なメッセージ・パッシング・システムです。 > > 評価：26人のユーザーによる評価は**4.3/5**。**おすすめ度**で最高の評価。 ----- ## 概要 ### IronMQの対象ユーザー デプロイメントとスケーラビリティの点で非常に柔軟性が高いので、中小企業からFortune 50企業まで、幅広い事業者がIronMQを導入しています。 ## 簡単な統計と評価 | 測定基準 | 評価 | 詳細 | | **総合評価** | **4.3/5** | 26 レビュー | | 使いやすさ | 4.2/5 | レビュー全体に基づく | | カスタマー・サポート | 4.4/5 | レビュー全体に基づく | | 価格の妥当性 | 3.9/5 | レビュー全体に基づく | | 機能 | 4.3/5 | レビュー全体に基づく | | おすすめ率 | 70% | (7/10 おすすめ度) | ## 企業情報 - **キャプテラについて**: Iron.io - **ロケーション**: Las Vegas, アメリカ - **設立**: 2014 ## ビジネスコンテキスト - **価格プラン**: $24.99 - **価格モデル**: (無料のトライアル) - **対象となる企業**: 自営業, 2～10, 11～50, 51～200, 201～500, 501～1,000, 1,001～5,000, 5,001～10,000, 10,000+ - **デプロイとプラットフォーム**: クラウド、SaaS、ウェブベース, Mac（デスクトップ）, Windows（デスクトップ）, Linux（デスクトップ） - **サポートされる言語**: 英語 - **利用可能な国**: アメリカ合衆国, イギリス, インド, オーストラリア, カナダ, ドイツ, ブラジル, メキシコ, 中国, 日本 ## 機能 - API ## サポートのオプション - メール/ヘルプデスク - FAQ/フォーラム - ナレッジベース - 電話サポート - 24時間対応（オペレータ） ## Category - [アプリ開発ツール](https://www.capterra.jp/directory/30082/application-development/software) ## 代替製品 1. [Salesforce Platform](https://www.capterra.jp/software/164356/app-cloud) — 4.4/5 (392 reviews) 2. [Domo](https://www.capterra.jp/software/119119/domo) — 4.3/5 (329 reviews) 3. [MuleSoft Anypoint Platform](https://www.capterra.jp/software/130185/anypoint-platform) — 4.4/5 (573 reviews) 4. [RunMyProcess](https://www.capterra.jp/software/1017065/runmyprocess) — 4.5/5 (6 reviews) 5. [Zapier](https://www.capterra.jp/software/130182/zapier) — 4.7/5 (3043 reviews) ## レビュー ### "Efficiency is the name of the game" — 5.0/5 > **Ryan** | *2019年2月15日* | インターネット | おすすめ評価：9.0/10 > > **良いポイント**: We run a pretty lean startup and need to offload as much development operations as possible. We looked at AWS of course and discovered IronMQ to be the right balance of functionality, ease-of-use, and cost. The Worker and MessageQueue products are particularly top-notch. > > **改善点**: It was difficult to migrate off of our existing infrastructure but the team at Iron tried hard to ease the pain. There's probably no way around it. Not everything will transfer seamlessly but we were able to do it with minimal downtime. > > We process millions of jobs a month and needed a way to scale outside of running our own Sidekiq instance. Worker and MessageQueue were the team that solved it for us. ----- ### "Set up a push queue in few minutes" — 5.0/5 > **Jose** | *2019年2月15日* | コンピュータ・ソフトウェア | おすすめ評価：8.0/10 > > **良いポイント**: Very easy to set up projects, queues, subscribers. Good value for money. > > **改善点**: The company seems to be quite focused on IronWorker and the product plans do not contemplate a low-volume case when you just need a cloud-hosted push queue server to distribute amongs subscribers. Documentation on local setup with Docker is limited. > > We needed a cloud-hosted push queue to distribute work across several worker nodes that we were hosting and ironMQ was the perfect solution. The Node.js sdk allowed us to set up very quickly the necessary code to send the jobs requests, and then you just need to set up your queue to push your messages to these subscribed workers. Another feature we liked was the availability of some Docker images that mimicked the authentication and queue behaviour for testing locally. We've used extensively in our docker-compose stacks. ----- ### "Evaluate with great caution and care before committing" — 2.0/5 > **Ezekiel** | *2019年2月15日* | インターネット | おすすめ評価：0.0/10 > > **良いポイント**: - Signed up on a free plan - Integrated easily with Heroku > > **改善点**: - Randomly lost queues several times during THEIR outages - Very slow performance - Horrible support; sometimes WEEKS without response - Horrible documentation -- out of date, incomplete, etc. - Minimal feature set -- not even close to competitors - Terrible, buggy UI online > > IronMQ at the time was the simplest integration for our small PHP Laravel app on Heroku. We are still stuck on it despite having grown significantly. Even when we were small we faced myriad horrible technical issues that should never happen with any production 3rd party service -- loss of data, frequent outages, god awful performance, buggy UI causing you to have to revert to your own API usage for simple queue management tasks, etc. I would never put it past a company to improve over time so I won't just tell you to run away as fast as you can, but SERIOUSLY if you ever are actually considering using Iron or someone tries to convince you to use it, you should be prepared to justify that decision against very mature, very serious competition at this point. Queuing is more or less a solved problem including managed solutions in the cloud; Iron doesn't hold a candle to the competition at this point in time. ----- ### "IronMQ let us quickly get to solving the problems that really mattered for our company" — 5.0/5 > **認証済みレビュアー** | *2019年2月15日* | ホスピタリティ | おすすめ評価：8.0/10 > > **良いポイント**: IronMQ was simple to implement in our system. We use it for a number of use cases and find it reliable, fast, and easy to use. > > **改善点**: I can't think of any specific issue we've had with IronMQ. When we first started we organized things in an awkward way which lead to a large number of projects appearing on the dashboard when logging into Iron. That was mostly our own fault though. ----- ### "Interaction with go driver is great\!" — 5.0/5 > **Diego** | *2019年2月15日* | 投資運用 | おすすめ評価：10.0/10 > > **良いポイント**: How easy it was to get up and running. At least the Go driver let's you put your config files in several places, following a hierarchy to override one value or another. > > **改善点**: This will sound like a fake review but my experience was just very good with IronMQ, there wasn't anything I needed that wasn't there. > > I wrote a search engine that had to coordinate several crawlers. I used IronMQ because I didn't want to setup any of the other message queues. I wrote my app in Go, and the go driver to talk to IronMQ was well designed, easy to follow examples on their site. The dashboard gives you enough info to debug any issues. Really good experience. ----- ページ：1 / 2\ 次へ: [次ページ](https://www.capterra.jp/software/182241/ironmq?page=2) ## リンク - [Capterraで表示する](https://www.capterra.jp/software/182241/ironmq) ## このページは以下の言語で利用できます | ロケール | URL | | de | | | de-AT | | | de-CH | | | en | | | en-AE | | | en-AU | | | en-CA | | | en-GB | | | en-IE | | | en-IL | | | en-IN | | | en-NZ | | | en-SG | | | en-ZA | | | es | | | es-AR | | | es-CL | | | es-CO | | | es-CR | | | es-DO | | | es-EC | | | es-MX | | | es-PA | | | es-PE | | | fr | | | fr-BE | | | fr-CA | | | fr-LU | | | it | | | ja | | | nl | | | nl-BE | | | pt | | | pt-PT | | ----- ## 構造化データ