I was traveling this past week (on vacation actually) & while waiting in the Dallas/Fort-Worth airport to catch a connecting flight I overheard a pretty sad telephone conversation between two engineers that really made me appreciate what our teams have designed & developed over the past 10-years. The conversation between the two software engineers went something like this…
“We are getting a number of customer complaints that the application keeps crashing their systems. Have you looked at the database queries that are running? You know the database is our Achilles’ heel man. We can’t support all that many simultaneous queries. Maybe we should trying queuing up the queries so they don’t overload the system? Yes, I know if we do that it will take longer for things to run, but better they run then crash all the time, right? You know table joins may be a problem too. The database just can’t handle queries that require table joins. Maybe the queries we are running are just too big… I don’t know man; we’ve got to do something soon to fix this. OK, try some stuff & get back with me. I’ve got to tell our customers something.”
I can’t tell you all how relieved I was that I wasn’t in this company’s position. My jaw about hit the floor when I heard the guy refer to their database as their Achilles’ heel. If there is one thing that our customers don’t need to worry about it is our database solution. Handling large volume database transactions is one of our core competencies to say the least. Our database solution handles millions of transactions daily without skipping a beat. These transactions aren’t from a single source either. We handle database requests coming from over 250 API methods, customer service web sites, reporting traffic, & obviously from systems applications handling call processing.
Transaction processing is just another one of the many solutions & services we offer & stand behind. We aren’t trying something new or untested either. We have a proven solution that continues to provide our customers with the reliability & scalability that enterprise solutions demand.
To conclude, I did consult with this gentleman about Jaduka’s Transaction Services API. He seemed overjoyed to hear that we had made our solutions available via simple Web APIs. His company obviously doesn’t have the time, money, or resources to develop a high volume database solution on their own & we’ve got a call later today to discuss this opportunity in more detail.