User:RobertKaye/3Scale Non Rate Limited Web Service: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
(New page: == Motivation, goals and measuring success == The motivations to create a non-rate limited web service are: * Allow us to keep track of commercial customers and charge for commercial acc...) |
RobertKaye (talk | contribs) |
||
Line 19: | Line 19: | ||
* Have their application successfully make non-rate limited requests of the ws/2 web service. |
* Have their application successfully make non-rate limited requests of the ws/2 web service. |
||
== Design == |
|||
== |
|||
The flow of requests through this improved service can be seen in the bottom half of this image: [http://tickets.musicbrainz.org/secure/attachment/10375/Untitleddrawing.png] |
|||
== Breakdown of tasks == |
|||
setup of the 3scale offerings |
setup of the 3scale offerings |
Revision as of 19:52, 9 March 2012
Motivation, goals and measuring success
The motivations to create a non-rate limited web service are:
- Allow us to keep track of commercial customers and charge for commercial access to our web service.
- Give end-users the option to pay for non-rate limited access to our web service so they can tag their music collection faster
The end goal of this project is to create two tiered service of our ws/2 (not ws/1) web service:
- where anonymous web service users get free service given the current limits.
- where people who have signed up with 3scale and have credit in their account get access to our ws/2 web service with no required pauses between requests, but are limited to X concurrent requests.
- where people who have signed up with 3scale, but have run out of credit in their account, simply revert back to the rate limited web service.
We will have succeeded if a developer can:
- Start with an existing application that uses the MB web service version 2
- Sign up for service at the MusicBrainz WS sign-up form hosted at 3scale
- Add the application/developer keys to their application.
- Have their application successfully make non-rate limited requests of the ws/2 web service.
Design
The flow of requests through this improved service can be seen in the bottom half of this image: [1]
Breakdown of tasks
setup of the 3scale offerings setup of varnish improvements to rate limiter