Question 9
Would IRCTC's railway ticket booking application be suitable for a serverless implementation?
No, because each use of the application by a prospective passenger for ticket search, date choosing, ticket seat blocking and ticket purchase is together a high complexity operation
No, because each use of the application by a prospective passenger for ticket search, date choosing, ticket seat blocking and ticket purchase will take a long time
No, because a failed step in the use of the application can result in duplicate payments
No, because the number of ticket searches cannot be scaled by simply running the application in multiple machines
No, because multiple prospective passengers have to use on a single machine (i.e. no embarrassingly parallel computation)