Kalibrr
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
AnsibleAnsible
at

All of our servers are provisioned by Ansible, with no manual provisioning involved. This lets us easily roll out new servers, with no chance for human error when configuring the servers. We use the same code to provision local development environments on Vagrant, which eliminates configuration discrepancies between development and production. Ansible

READ MORE
2 upvotes1.7K views
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
New RelicNew Relic
at

We monitor and troubleshoot our app's performance using New Relic, which gives us a great view into each type of request that hits our servers. It also gives us a nice weekly summary of error rates and response times so that we know how well we've done in the past week. New Relic

READ MORE
1 upvote16.2K views
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
InfluxDBInfluxDB
at

Server and application metrics are all stored in InfluxDB for capacity planning and anomaly detection. InfluxDB

READ MORE
1 upvote11K views
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
Amazon SESAmazon SES
at

Our internal emails (such as exception notifications) are sent via Amazon SES, since it's cheaper than using Sendgrid. We also use Amazon SES as a fallback in case we have deliverability issues with Sendgrid. Amazon SES

READ MORE
1 upvote10.6K views
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
HubotHubot
at

We have our own special Hubot instance named kbot, that does everything from reminding us what to do, showing cat and corgi images, and notifying us of system errors. Hubot

READ MORE
1 upvote8.5K views
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
TornadoTornado
at

We use Tornado as our websockets server, using SockJS (an alternative to socket.io). Tornado

READ MORE
1 upvote8.5K views
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
Amazon Route 53Amazon Route 53
at

Amazon Route 53 is a convenient way to manage our DNS routes. We just use the web UI for now, since we don't have any complex DNS setups. Amazon Route 53

READ MORE
1 upvote8.4K views
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
NagiosNagios
at

Each piece of our infrastructure is monitored using Nagios, alerting us immediately if anything goes wrong (hopefully before anyone else notices), and with a level of granularity that really helps in resolving things quickly when things are on fire. Nagios

READ MORE
1 upvote7.9K views
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
PugPug
at

We use Jade when writing HTML, which is much easier to read and maintain. We compile it to HTML before deploying it though, and don't use Jade's client-side rendering features. Pug

READ MORE
1 upvote7.3K views
Avatar of TimDumol
Lead Software Architect at Kalibrr
Shared insights
on
NexmoNexmo
at

We fall back to Nexmo when Chikka (https://api.chikka.com) and Semaphore (http://semaphore.co) have downtime or deliverability problems. Chikka and Semaphore are local (Philippine) SMS APIs handled by SMART and Globe, respectively, and report higher deliverability rates than Nexmo (at lower cost). Nexmo

READ MORE
1 upvote6.8K views