| |May 201719CIOReviewCost savings are a byproduct of a good serverless implementation, rather than the reason to go in for the sameservers in parallel. We have as many servers up and running as are combinations of chains and manufacturers, and should these combinations increase, we would still be within the same 3 to 5-minute window. When all the parallel jobs complete, notifications are sent to the appropriate teams using the notifications service: this is both email and SMS based. The entire solution was designed and completed within 2 weeks.So what have we established? Split the job using multiple parallel servers that run for a few minutes only. This is pure serverless triggered by a storage "PUT" event. Once this data is in the cloud database (also run by a database service), we need the executives at the stores to access this. For this we use the API gateway service, which is completely RESTful, and has the basic elements of security, metering and throttling. So we have a simple solution, developed in an agile manner, using services that are guaranteed to have high availability and throughput, executing in a controlled workflow environment, without compromising on the risk. All this results in a time saving in excess of 95 percent for the hundreds of executives we have at the stores across the country. This is the true business case.Still, let us not forget the numbers. We do this job 10 times a month, each time we do a test on a UAT environment and a final run on a Production environment. So, a total of 20 runs per month, with each run not exceeding 3-5 Rupees. My overall cost per month is not more than 100 Rupees (less than 2 US$). As I wrote at the start, cost savings are a byproduct rather than the reason for undertaking the transformation to a serverless solution.
< Page 9 | Page 11 >