Rogers Catalyst

 
null
29
Jun
2011
 

API Rate Limiting Demystified

Posted by Vishal
 

About this Blog Post

Rate limiting is a measure of number of API calls allowed in a given period of time. With adoption by Yahoo, Twitter and Facebook, Rate Limiting has emerged as a best practice that allows web service providers to manage scale and service availability of the service. In this blog post I will shed some light on how rate limiting works for Rogers Catalyst.

Developer Profile and Project

As part of your Registration process at www.rogerscatalyst.com, you are required to create a Developer Profile and one or more Projects associated with your Developer Profile. The Developer Profile represents your business entity and the project represents your application. 


TPS and Projects

Every project is associated with a policy that allows us to manage the business relationship with the developer. One of the attributes of this relationship is the allowed Transaction Per Second (TPS) rate. As the name suggests, TPS is a measure of the number of API calls allowed in one second and this is the mechanism for implementing Rate Limiting for Rogers Catalyst.


Sandbox vs. Production TPS

When you get set up on Catalyst your project is allocated a Sandbox policy. In the Sandbox your project is allowed 1 TPS. When you are ready to launch your project you can push your project to Production. In Production mode the default policy allows up to 3 TPS.  It is important to note that the TPS rate works at a project level so if you have two projects in Production you have access to 3 TPS for each project.  This is another reason why it is a good idea to build each service as a separate project.

Staggering API Calls

Although in theory your application can push the maximum TPS allowed by your policy, you are more likely to get better performance if you stagger your API calls. In the event you receive a rate limiting error, you should reduce the rate at which you are submitting transactions and re-try. This situation has most likely arisen because your application server’s clock is not synchronized with the Catalyst clock so for any particular run the one-second window on the application server might not overlap with the one second window on Catalyst server. This is especially applicable for applications that do bulk or batch transactions.

 
 
 

 

null
16
Mar
2011
 

Location Based Services: The Real Deal

Shop Alerts launched by Mobile Fringe for their Push a Deal app using Location API.

 
 
 

 

null
10
Mar
2011
 

Exciting news in the Rogers Catalyst world....

Neustar moves to Production.

 
 
 

 

null
4
Mar
2011
 

Be RESTful with curl PART-2

Posted by Vishal
 

“Be RESTful with curl" series of blog posts are my chronicles of leraning about Rogers Catalyst APIs. These will be particularly useful for you if you are taking a first stab at the APIs. In this post I will use SMS RESTful API to send a text message to a mobile phone from my dev virtual machine. 

 
 
 

 

null
28
Feb
2011
 

Be RESTful with curl PART-1

Posted by Vishal
 

As a Rogers Catalyst newbie I will be doing some serious hands on platform APIs to develop a deep expertise on the APIs as well as broad know-how around how applications and services are developed with the Rogers Catalyst platform. “Be RESTful with curl” series of blog posts are my chronicles of this learning process. This will be particularly useful for you if you are taking a first stab at the Rogers Catalyst APIs or if you want to learn to use curl to interact with RESTful web services. Part 1 of this series will deal with Location and Privacy APIs


 
 
 

 

null
17
Feb
2011
 

Greetings Everyone !

Posted by Vishal
 

My name is Vishal Arora, and as of today I have joined the Rogers Catalyst team as Product Development Manager.  My main focus this year will be to drive awareness and adoption of the Rogers Catalyst platform. I am going to achieve this by engaging the development community, creating a thriving ecosystem and providing an unparalleled customer experience. 

 
 
 

 

null
9
Dec
2010
 

In-App Payments to Rise in 2011

Posted by cglynne
 

A recent report from Bango is predicting that In-App payments will see a 600% revenue growth in 2011. This is a huge opportunity for application developers to generate new and enhanced revenue opportunities. [more]

 
 
 

 

null
30
Nov
2010
 

Planned System Maintenance

Posted by cglynne
 

We will be performing scheduled maintenance on Rogers Catalyst starting at 10PM EST on Dec 1 until 6AM EST Dec 2. You may experience service degradation or service outages during this maintenance window.

UPDATE:

 
 
 

 

null
11
Nov
2010
 

Welcome to Rogers Catalyst Beta!

Posted by cglynne
 

We have been working for a while now to bring you capabilities that will enable you to easily leverage the power of Operator Network resources in your Cloud based applications and services.

 

 
 
 

 

Twitter

Off The Blog