What people recommend, in their own words, with the receipt.
Question-and-answer site for programmers, run by Stack Exchange / Prosus.
10 things
TerraformSoftware
We are using Terraform to build all our cloud resources so it was relatively easy to spin up additional environments that matched production.
Stack Overflow on building its cloud environments with Terraform
stackoverflow.blog ↗·2025-08-28Wrong?
Octopus DeployService
For deployment, we’re doubling down on Octopus Deploy.
Stack Overflow on deploying the public platform with Octopus Deploy
stackoverflow.blog ↗·2025-08-28Wrong?
SQL ServerSoftware
Our public sites have always used SQL Server, which we’ve optimized to have very high throughput.
Stack Overflow on keeping SQL Server for the public sites
stackoverflow.blog ↗·2025-08-28Wrong?
FastlyService
Fastly gives us control over routing/redirection, as well as things like request/header manipulation, certificate management, failover between regions, and request logging and observability.
Stack Overflow for Teams on keeping Fastly in front of its Azure environment
stackoverflow.blog ↗·2023-09-05Wrong?
Azure Cache for RedisService
As you’ve learned throughout these blog posts, we did a lift and shift and deliberately decided to not adopt cloud native elements yet (except Azure Redis, which just worked).
Stack Overflow for Teams on the one cloud-native piece it adopted during its Azure lift and shift
stackoverflow.blog ↗·2023-09-05Wrong?
KubernetesSoftware
We had already made the decision to use Kubernetes as the core application hosting platform for all services, which aligns with our overall broader adoption of Kubernetes since moving Stack Overflow for Teams to Azure.
Stack Overflow on moving the public sites to the cloud and standardising on Kubernetes
stackoverflow.blog ↗·2025-08-28Wrong?
CloudflareService Cloudflare
Instead, we planned to move all public assets behind the Cloudflare CDN and process the logs with Snowflake.
Stack Overflow on putting public assets behind the Cloudflare CDN
stackoverflow.blog ↗·2025-08-28Wrong?
PackerSoftware
So we decided to invest in building VM base images with Packer that we could easily update and deploy.
Stack Overflow for Teams building web VM images for Azure
stackoverflow.blog ↗·2023-09-05Wrong?
SQL ServerSoftware
On-premises, we ran SQL Server installed on a VM in an availability group that spanned our two on-premises data centers.
Stack Overflow for Teams database before moving to Azure
stackoverflow.blog ↗·2023-09-05Wrong?
RedisSoftware
On-premises, we install and manage Redis ourselves on a bunch of Linux servers.
Stack Overflow for Teams on self-managed Redis on-premises
stackoverflow.blog ↗·2023-09-05Wrong?
Elastic CloudService
However, when we started loading more data, we ran into issues where ElasticCloud would become unresponsive and master nodes randomly failed and didn’t come back up.
Stack Overflow for Teams on why it left managed ElasticCloud for self-run Elastic
stackoverflow.blog ↗·2023-09-05Wrong?
Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.
The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.
A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.
The small bar beside a date shows how dated a recommendation is for its kind of thing.
The bar shows how dated a recommendation is, for its kind of thing. Full and green is recent. It drains, and turns amber and then grey, as the post gets older.
What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The bar is empty after about:
A striped bar means the post carries no date and the date shown is an estimate. No date at all, no bar.