We're in the process of moving our Tessy environment to new servers (Windows 2012 r2 paired with SQL Server 2014). In our existing environment the payment gateway service lives on its own server. Having since moved away from Transcend, we no longer require this particular server...so we're hoping to consolidate. In our environment this basically means either our REST/SOAP gateway server (or) tessitura db server.
I have asked Tessitura in the past if either location is more ideal and was told that either is fine so long as you have the resources. Though we do have ample scalable resources (virtual servers) and I like the idea of housing the pmt gateway on our rest/soap server overall, high on sale situations have potential to really slam the API...which leads me to believe that the database server may be a better location overall.
I plan on doing stress testing once all systems are configured, but am hoping to make a good informed decision before getting to that point.
All that said, I'm curious what ya'll's setup is like (and why)?
Thanks!
Very true about resource utilization on database server...it's something to consider...
Actually the main reason I am leaning toward moving the payment gateway to the database server is because in prior load testing of our systems, high load eventually causes bottlenecking to occur at the SOAP/REST server long before the database server ever becomes "problematic".
SOAP/REST can really demolish CPU resources if given the opportunity and the application queue builds. Under a heavy load scenario, you could have a situation where the payment gateway is competing for the same resources as SOAP/REST, making the issue that much worse. Theoretically anyway. =)
'Course a bottleneck will occur somewhere at some point no matter how you shuffle things around.