◷ Reading Time: 3 minutes
Navigate to the package Builder window in FlexRule Designer and make sure you deploy multiple service versions under a single package file settings.
Specify Service Settings
In each deployment destination (AWS, Azure, Google Cloud), you will find following highlighted section to specify the service weight and database connections string to save the service execution stats.
Service Weight : Add weight and connection string to all the service versions in the package.
Database Connection String : You can use either MSSQL or PostgreSQL database in order to store the service execution stat.
Sample Database Connections Strings as follows:
Data Source=XXX;Initial Catalog=FRS;User ID=XXX;Password=XXX;MultipleActiveResultSets=True
Access Service End Points
Once the first service deployment is completed you can see the completed status in the Background Task section.
You can use the Champion Challenger Service Execute Url to access the Champion Challenger service end point.
And also you can access the other urls as we access normal deployment urls.
Update an Existing Champion Challenger Package
Once you successfully deployed your first service using Champion Challenger settings, for the rest of the different service versions, you need to update the service with different service versions. Once you update the service, make sure you use same package Identifier and Package version for your different service versions.
Repeat the steps to add Weight to all service versions in the package and use same Database Connection String.
Click here to read more about how to update an existing app.
Call API Endpoint
When you execute your services (using Champion Challenger Service Execute Url), you will notice that a proportion of requests will go to each service version based on the weights that have been set.
You can check the statistics of the database table which you used for Database Connection String. You can find a table called “ServiceRunStats“. It will show you your different service versions against Service Id.
Sample data for ServiceRunStats table as follows for 5 different service versions.