scp756-221 / term-project-alpha Goto Github PK

1. Use K8S to deploy the new playlist service on AWS EC2 instance

1. Create a new service(s3) for playlists with mock data such as (music.csv)
2. Make the server run on your local system
   Refer to Assignment 1 for more information

Create a draft for Interim report on a cloud platform such as Google Doc and share document URL with editor access rights to everyone in the team.

Test the load balancing capability of the application with up to a load of thousands of users (e.g, >1000 users) and hundreds of thousands of requests (e.g., >100,00 requests/second). use Gatling to create the synthetic load

Get started with gatling setup and execution on existing service according to guide 1 instructions

Setup and get accustomed to Prometheus

1. Understand how and where the data is stored in the existing Services(User/Music)
2. Find out the changes needed to save new data in the Dynamo DB

1. User should be able to add songs to the playlist.
2. Add test cases for the new functionality

1. Visit the Gatling URL from the project document and understand the working of Gatling
2. Complete module 1 of Gatling

Get accustomed with Grafana and Prometheus

1. Users should be able to create their own playlists
2. Add test cases for the new functionality

Getting accustomed with Service mesh and Istio

Follow the given guides in the project document to setup Grafana

Setup and get accustomed to Service mesh and Istio

temp inside

In the newly created Playlist service add a function Delete a particular playlist

Setup the requisites to work with Gatling on local machine and get accustomed with the scripts to run various load test cases.

1. Create a docker image of the new service s3
2. Deploy docker image to AWS EC2 instance

1. Understand the working of User Service
2. Understand the working of Music Service

Playlist service has create, read, update, delete functionality. Add API hit points like this for all the services in ReadTables.scala file

1. Leverage the newly created service s3 for playlists and migrate it to AWS
2. The client should be running on your local machine
3. Avoid making changes to client (mcli) code and make use of the AWS EC2 access URLs.