The only place state lives. Some basic database triggers simplify an awful lot of stuff that would be huge amounts of code in an MVC architecture.

Core language for both the presentation and the API tier.

Dev and live. It just makes sense.

A bunch of lightweight containers, huddling together for warmth.

On the presentation tier, for caching of "display fragments".

Client-side, basically for things like data-tables.

Host OS for most of our docker.

Client-side, because, well, browser-support.

Makes dynamic graphing so much easier.

Obvious choice of hosting.

For balancing the presentation tier, and for SSL offloading (which is great for performance.)

Using MySQL with Amazon doing the DBA admin.

Very simple usage - standard classes only (no SASS.)

Private repos, sorry.

Running a Kanban methodology in dev.