Hacker News Reader

Comment by mdaniel | Hacker News Reader

My years of scar tissue with RabbitMQ have given me a healthy suspicion of OTP ( https://git.pleroma.social/pleroma/pleroma#otp-releases-reco... ), and I would never want to be responsible for keeping it alive and healthy. For comparison, while I'm sure people also have strong opinions about rails and sidekiq, at least there is a non-trivial body of existing blog and SO posts about it

View on HN

That's odd given OTP's focus on stability and reliability.

RabbitMQ has been my message bus of choice for over a decade. Configuration is a total PITA, but it's a one-time thing. Otherwise, it's been rock solid and I'll happily continue to use.

I've been working on Elixir sites for years now and have never had an issue with OTP underneath, although none of them (yet) have been high-demand. The reliability and performance characteristics have been top-notch. Is it possible that with the mass influx of Elixir users into the Erlang space since the RabbitMQ days, OTP has made leaps and bounds of improvement?

That's fair. I selfhost Pleroma as a single-user instance, so I couldn't tell you about running it at scale. I went with it because it could run on a raspberry pi a few years back whereas mastodon was too resource-hungry.

I thought OTP was supposed to have a very strong operations/reliability story ("nine nines of reliability in telecoms" and all that)?

For what it's worth, I remember someone shared Pleroma code in the Elixir forum and some veterans there said it was a very non-standard way of organizing an Elixir codebase.

It could be possible that Pleroma is not very idiomatic Elixir / OTP.

Reply on news.ycombinator.com