Why so many *arr services? Why not 1 service that works with all media types?

YorddleZiggs@lemmy.dbzer0.com to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com – 126 points –

I am almost done building my first self hosted streambox through Docker. That's a total of 16 instances, each fulfilling 1 specific role.

As I'm new to the *arr world, could you please help me understand why it is standard to deploy multiple *arr services for each media type (ex: readarr1 for books + readarr2 for audiobooks) instead of using 1 that does multiple media types?

Thank you.

38

You are viewing a single comment
View all commentsShow the parent comment

Sure but they also seem to share quite a bit of GUI code at least. Couldn't all of these just be plugins for a core *arr service?

I think the goal of the original project (I think it was Sonarr?) was just to cover TV shows. The others had forked and the rest is history. It was never aimed to be a multi platform thing.