Kalibrr

Decision at Kalibrr about Ansible

Avatar of TimDumol
Lead Software Architect at Kalibrr
AnsibleAnsible

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

1 upvote15 views

Decision at Kalibrr about New Relic

Avatar of TimDumol
Lead Software Architect at Kalibrr
New RelicNew Relic

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

1 upvote10 views

Decision at Kalibrr about Nexmo

Avatar of TimDumol
Lead Software Architect at Kalibrr
NexmoNexmo

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

1 upvote9 views

Decision at Kalibrr about HAProxy

Avatar of TimDumol
Lead Software Architect at Kalibrr
HAProxyHAProxy

We load balance our ElasticSearch cluster using HAProxy. The health checks come in handy. HAProxy

1 upvote6 views

Decision at Kalibrr about Tornado

Avatar of TimDumol
Lead Software Architect at Kalibrr
TornadoTornado

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

1 upvote6 views

Decision at Kalibrr about Hubot

Avatar of TimDumol
Lead Software Architect at Kalibrr
HubotHubot

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

1 upvote5 views

Decision at Kalibrr about Amazon S3

Avatar of TimDumol
Lead Software Architect at Kalibrr
Amazon S3Amazon S3

All file uploads go straight to Amazon S3 (with maybe some preprocessing). Amazon S3's cheap and easy-to-use, with no need to worry about disk space limits. Amazon S3

1 upvote5 views

Decision at Kalibrr about Amazon SES

Avatar of TimDumol
Lead Software Architect at Kalibrr
Amazon SESAmazon SES

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

1 upvote5 views

Decision at Kalibrr about InfluxDB

Avatar of TimDumol
Lead Software Architect at Kalibrr
InfluxDBInfluxDB

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

1 upvote5 views

Decision at Kalibrr about Amazon Route 53

Avatar of TimDumol
Lead Software Architect at Kalibrr
Amazon Route 53Amazon Route 53

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

1 upvote5 views