Łukasz Korecki

We use collectd because of it's low footprint and great capabilities. We use it to monitor our Google Compute Engine machines. More interestingly we setup collectd as StatsD replacement - all our Clojure services push application-level metrics using our own metrics library and collectd pushes them to Stackdriver

We use Google Compute Engine because it's developer centric, easy to use, yet really powerful. Comparing to AWS (which we originally stared with) it's more approachable, while having no obvious tradeoffs.

We use nginx because it's super reliable, has great extensions and at the same time is light-weigh​t. nginx powers our authorization layer, inter-service communication, and public load balancing (fronted by Google Compute Engine load balancers).

We initially chose RethinkDB because of the schema-less document store features, and better durability resilience/story than MongoDB In the end, it didn't work out quite as we expected: there's plenty of scalability issues, it's near impossible to run analytical workloads and small community makes working with Rethink a challenge. We're in process of migrating all our workloads to PostgreSQL and hopefully, we will be able to decommission our RethinkDB deployment soon.

We use Clojure because of simplicity, performance and great fit to our problem domain: processing a lot of structured data. Based on my experience so far, Clojure is my go-to language for most tasks, except for when a fast startup time and a low resource footprint is required - basically CLI tools. That's slowly starting to change thanks to native-image and GraalVM

We use Stripe because of ridiculously simple it is to integrate, while still supporting all kinds of billing scenarios.

We use Google Cloud SQL for PostgreSQL because it just works. The only dow​nsid​e is that it doesn't (yet) support the latest PostgreSQL versions.

We use RabbitMQ because of great stability and client support across many languages. RabbitMQ is the backbone of the whole platform and we use it whenever it makes sense (async background processing, event tracking, orchestration)

Ruby is the original language at Enjoy: the prototype was built with Ruby and some of its parts are running till this day (I'd say 80% of it is gone, ported to Clojure)

Outside of usual web-development tasks we use Ruby for our operations tooling.

We use Sass because it makes working with CSS somewhat easier. We use it both as part of Rails' frontend and via webpack/node.