> ton of traffic This comes with assumptions. Depending on the magnitude of the traffic you need very different architectures. For example, see Pokemon Go htt

> ton of traffic This comes with assumptions. Depending on the magnitude of the traffic you need very different architectures. For example, see Pokemon Go https://cloudplatform.googleblog.com/2016/09/bringing-Pokemon-GO-to-life-on-Google-Cloud.html https://cloudplatform.googleblog.com/2016/09/bringing-Pokemo... > an API How flexible should the API be? For example, do you need multiple representations (JSON, YAML, XML, etc)? Maybe it makes sense to build it representation-agnostic, but maybe it is over engineering.