Architecture from website to database

Would anybody be prepared to describe the architecture of their Tessitura setup?  There is now a whole range of options for the construction of the Tessitura system from end to end.  We chose to host it all in house several years ago.  However organisations now can host on premise, in the cloud, implement a hybrid arrangement, use the packaged options that Tessitura offers such as RAMP, RADR, TNEW.  What are the benefits and pitfalls of each different setup?  How has this altered the skill sets required in house, or the costs of maintaining the systems, the performance of your website or the resilience of your whole system? 

I would be keen to get people from organisations with a range of different architectures that are prepared to share their experiences and opinions.

Thanks,

 

Chris