The emergence of thick-client websites – how to identify and performance test them
We’re seeing more thick-client development approaches to designing on the web, websites that behave like mobile apps – and they present many challenges to traditional performance engineering practices, so how do you identify and tackle those sites?
We have seen an interesting reversal of traditional web Vs mobile site development. In the past, many developers would shoehorn full blown websites into mobile frameworks like Cordova, Sencha, etc. We’re now seeing developers take full-blown mobile application architectures and shift it to the web, placing that application architecture within the browser – a ‘thick’ web client.
We will discuss these thick-client websites, how they present themselves, how they’re structured, how they function, how to performance test them. Some of the most difficult issues are with how the customer wants to approach testing and setting expectations. What does this mean to us as practitioners of performance engineering, and what tools do we bring to this situation when it presents itself to us? There’s more than one way to approach this situation, and we’ll talk through some of them.
Brian has worked in this field since the mid 1990’s; contracting to Mercury, working on their Expert Services team, eventually specializing in APM and performance engineering solutions at Mercury. ATS/VIP, J9 Technologies, SOASTA, Keynote, Dynatrace, and now Foulk Consulting.