LocalyticsEng

At Localytics, data is central to our mission. One of our core principles is to"lead with data." When I envision that, I often think of an analyst using graphsto make a case for a business decision, or a principal engineer using benchmarksto advocate for

At Localytics we build command line interfaces that manage our infrastructure and processes. This is our list of best practices that we've learned.

The engineering managers at Localytics have been working together for over ayear, and through ups and downs, we've grown and learned a lot as a team. Thegoal of this post is to share some of the lessons we've learned with thecommunity. Some of the content

We believe the highest performing engineering teams have a process to identify,triage, fix and learn from service degradations and downtime. At Localytics, webuild highly available and scalable systems, and part of the key to our successis learning from f

Today we are open-sourcing Humidifierhttps://github.com/localytics/humidifier/ - one of the tools that we useinternally to manage infrastructure on Amazon Web Services (AWS) at Localytics.This Ruby gem allows you to programmatically generate domain object

In January and February of this year we open sourced three SBT plugins that havehad a huge impact on our ability to test our AWS based Scala microservicesarchitecture: sbt-s3 https://github.com/localytics/sbt-s3 sbt-dynamodb https://github.com/localytics/

As you may have read in our previous posts (herehttps://eng.localytics.com/vertica-at-scale-in-aws/, herehttps://eng.localytics.com/performance-in-big-data-land-every-cpu-cycle-matters-part-1/ and herehttp://https://www.google.com/url?q=http://eng.localyt

Today Localytics is open sourcing two tools that help you quickly scaffoldcustom Slack commands using AWS Lambda, AWS API Gateway, and the Serverlessframework. These tools grew out of our continued investment in making ChatOpsthe primary way Localytics en

Let's continue to explore the idea that