Some News About Musicbrainz-Mirror

Hey People!

Almost a year after my initial post in 2014 I wanted to talk to you about some things that have happened since back then. =)

First, I want to apologize for all the downtime lately. It has been necessary  to update the server to the newest MusicBrainz VM released on 2015-08-06 and to put a loadbalancer in action.

Yes, you heard right! Now a loadbalancer splits the traffic evenly among two individual mirrors, which should increase the availability and response times allot.

As you guys also care about the data beeing up-to-date, the servers are setup to automatically reindex the database, taking turns on a daily basis. This way there always should be at least the power of one server available at your service while the other one is updated.

How to get your search done you ask? Just use http://musicbrainz-mirror.eu:5000 as always.

Last but not least, I want to thank all the people who did send me delivered food and beer by using the “Chip-In” button on the right hand side of this page. You helped me through all those hours of headache setting everything up! Highly appreciated! 😉

Cheers

Tobias

8 thoughts on “Some News About Musicbrainz-Mirror”

  1. Hey, I’m so glad I’ve found this. Echonest API is dying since they were absorbed by Spotify and I was looking for an alternative for them. Musicbrainz has some of the data that I need and I’ve decided to give it a try but bumped into the throttling and rate limit from the official server. I got a docker image for the musicbrainz server and got it up but I still faced the rate limit and throttling and didn’t find any documentation on how to disable these on my local server. Is there any config for that? Did you fuss with the server code? Are you planning to keep your server up for long? I’m wondering if I should go on with setting my own server up or if it’s ok using yours. Do you have any rate limit or throttling active?

    1. Hi Gabriel!

      I am currently running the official musicbrainz vm pretty much untouched. One instance on VMWare and one I transferred to a physical server. The only limitations my setup has, are purely physical, like CPU and IO on storage. I don’t even think there are any configurable values for throttling in the vm. At least none that I found?
      It is in no way high performance, but it gets the job done for me and a lot of other users, as it seems.

      How much requests will you be making at what rate? The uptime is good since it runs on two machines, but the response times still vary alot. Please feel free to try if it works for you and doesn’t kill the service. 🙂

      I did set up this mirror, because I myself needed a MB instance without rate limiting for a project of mine that is actively using it. There are no plans whatsoever on taking the service down, but if you need something really really reliable, I would advice you to setup your own server, as there are no guarantees here.

      Best regards

      Tobias

      1. I didn’t try the VM, I tried a docker image (https://github.com/linuxserver/docker-musicbrainz) and after a few requests to it I started getting a “Rate Limit Exceeded” message which was way too frustrating. My own server was rejecting my requests and when looking for a rate limit config I found your mirror.

        I’m not sure yet if your server will be enough for my demands but it’s surely working better than the official one. I haven’t tried it out for real as I’ve found out musicbrainz isn’t a very good replace for the echonest API. I’m still trying out mixing some APIs to find a better solution then I’ll do real tests with your servers.

        About my requirements, I surely won’t be making calls all the time , first because I’m far from having a heavy load, second because I cache all external requests and third because part of the data that I fetch is immutable so I don’t need to refresh it. The thing is that when I need data I usually make a ‘lot’ of concurrent requests, around 100 in case I have nothing cached, because I need data about lots of artists to fulfill a single user request and I would like that to be quick.

        Maybe MusicBrainz has a feature for multi searches in a single requests but I haven’t studied it much yet. In case you have experience with it and are willing to help me out, my current problem is that Echonest provided me the start date for an artist career and I need to get it somewhere else now. It seems that MusicBrainz has the start date for a GROUP but when it comes to a solo artist it returns the BIRTH date, which is a very different information. I’ve tried looking for albums by the artist and checking the first date but it doesn’t work quite alright. Echonest says Tori Amos started in 1979 and so does wikipedia, her first released solo album was in 1992. I’ve considered looking for info on wikipedia but I’m not sure it’s a good idea, I might have lots of trouble with disambiguation, there are all sorts of artists with weird names and wikipedia has pages about everything.

        Sorry about the long post 😛 No clue if you find this kind of thing interesting or boring.

        May I ask you what you’re using MB for?

        1. Partially answering my own question: I fell in love with Discogs API. Still not getting results as good as echonest but much closer than with Spotify or MusicBrainz and it’s also quite flexible.

Leave a Reply

Your email address will not be published. Required fields are marked *