Hello,
There has been talk that the API can only handle 200 - 300 connections at a time and it bottlenecks if it goes higher. I ask because we experienced something similar during a big ticket sale last month (hundreds of people trying to hit the website at the same time). Has anyone experienced anything similar and if so how did you compensate for it?
We had a large on sale this past fall that stressed our environment. While we did have some bottlenecks with the Web API, our bigger problem was with the seat server.
Our web site currently only enforces per line item limits on the number of tickets. What we ran into was web patrons were adding multiple sets of seats to their cart in an attempt to find "better" seats, and then would abandon their cart which would leave the seats locked until they timed out. This caused some stress on the seat server.
We are working with our web integrator on a waiting room as well as some better ticket limit enforcement to reduce these issues for our next major on sale.
-steve carlock
Information Technology Manager
The Granada
(805) 899-3000 x 111 (phone)
(805) 899-3081 (fax)
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Robert MartinSent: Wednesday, January 12, 2011 12:47 PMTo: Steve CarlockSubject: [Tessitura Technical Forum] Web API