Testing Overview

Hardware Resource Usage

Jetstream Instance	M3.medium
CPU Cores	8
RAM	30 GB (out of which 11 GB is used by instance buffer/cache)
Disk	40 GB

Number of Requests Tested for Each Microservice

Data Service	Up to 100 requests
Auth Service	Up to 250,000 requests
Registry Service	Up to 250,000 requests
User Service	Up to 250,000 requests
Database Service	Up to 250,000 requests
Gateway Service	Up to 250,000 requests
Frontend Service	Up to 250,000 requests
Metadata Service	Up to 250,000 requests

Expected Throughput

We expect the microservice throughput scores to be significantly higher (10 times more) than our data service which is our heaviest microservice doing most of the heavy lifting in terms of fetching the data from S3 buckets and generating the graph based on the user input query at the ‘/widget’ endpoint.

Estimated Usage of Resources

All microservices except the data service, operate with low RAM utilization which is maximum 250Mi. Data service utilizes the entire 5000 Mi allocated for each pod in the pod definition file.