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!
Unknown said: We're in the process of moving our Tessy environment to new servers [...] All that said, I'm curious what ya'll's setup is like (and why)?
We're in the process of moving our Tessy environment to new servers [...]
We've recently consolidated some of our servers as well, since they were all VMs on the same hosts anyway, and just moved the PGS service to the database server this morning. We are down to the db server and WebAPI server. Moving the seat service, PGS, and application services IIS sites to the db server has resulted in small, but noticeable performance improvements. We aren't missing the separate servers at all.