[seanjregan]

The back-end has been getting totally rebuilt as part of this. The move to AWS has opened up a lot of options also. For example, we can take advantage of:

* elastic scaling, * large in-memory caches like memcached, * data locality, * alternative data stores better suited to our data structures such as dynamoDB, * different instance sizes, * dedicated asynch batch processing nodes, * specific instance sizes suited to specific workloads, etc etc

We are also optimizing how and where we store data. We are already storing data in different AWS regions (closer to our customers), however, we are going to also start getting smarter about ensuring the data is actually in the optimal region for the majority of users on a site.

There is also room for improvement in tuning how we query data for issues with many fields, or instances with very with complex permissions enabled. This will require optimizing the SQL we use to retrieve data, to provide all we need to render a Jira issue as fast as possible and exploring other storage technologies for fast data retrieval.