Scenario 01: Rate Limiter Service with RL Cassandra Counters Implementation*
Scenario Description
The intent of this scenario is to validate to RL effectiveness using distributed RL counters in Cassandra Keyspaces.
Version Control
| Version # | Date | Author | Description |
|---|---|---|---|
| 0.1 | 10/12/2011 | Jose Alvarez Muguerza | Initial Draft |
Use Case
Have two jetty servers deployed with echoservice, two other jetty services deployed with RL service, and two seperate cassandra instances. Have a client talk to echo service instance 1 in jetty1, and then instance 2 in jetty 2. Jetty1 instance talks to RL instance 1, jetty2 talks to RL2. RL1 and RL2 randomly talk to either cassandra 1 or cassandra 2. Actually we have 4 cassandra nodes running as External Cassandra services
The calls to the echoservice should be done using RESTful name value queries. 
Use Case Services Involved.
The following services will need to be used besides the Rate Limiter Service:
This test scenario covers the following high-level test components/requirements
- Rate Limiter Service
- Policy Service
- Authentication Service
- Policy Admin UI
- Turmeric Utils (turmeric-cassandra-util-jar)
- an EchoService
Use Case Additional Requirements
- Latest Jetty-Turmeric distro
- Cassandra 0.8.2
- MySql 14.14
- Sun JDK v1.6
Environment Setup:
Test Scripts
The following scripts will cover this scenario:
Script 1.1: RL Counter in cassandra - Two policies, simple rule