* Service for taking snapshots of websites (in production)
* noeqd (not our code, but it is in production, and written in Go)
* Webhook delivery service (production later this month)
* Stats server for storefront statistics (in development)
* Some reporting-related service I don't know much about (in development)
* bucket-to-bucket sync tool for S3 (command-line tool)
* Image resizing service (likely to replace our existing service written in ruby next time it bottlenecks)
We don't currently have a ton of deployed Go infrastructure, but a lot of new development is happening in Go. We've hit a point in our growth where it makes sense to start thinking about fast services rather than throwing more job servers at the problem, so a few things are being extracted to new Go services here and there. We intend to continue along this line, using Go where we'd like more performance (concurrency) than we can trivially get out of ruby, or if it feels like it fits the problem domain.
* Service for taking snapshots of websites (in production)
* noeqd (not our code, but it is in production, and written in Go)
* Webhook delivery service (production later this month)
* Stats server for storefront statistics (in development)
* Some reporting-related service I don't know much about (in development)
* bucket-to-bucket sync tool for S3 (command-line tool)
* Image resizing service (likely to replace our existing service written in ruby next time it bottlenecks)
We don't currently have a ton of deployed Go infrastructure, but a lot of new development is happening in Go. We've hit a point in our growth where it makes sense to start thinking about fast services rather than throwing more job servers at the problem, so a few things are being extracted to new Go services here and there. We intend to continue along this line, using Go where we'd like more performance (concurrency) than we can trivially get out of ruby, or if it feels like it fits the problem domain.