State Farm Engineering

Information contained in the articles on this site may not be representative of actual use cases. The views expressed in the articles are personal views of the author and are not necessarily those of State Farm Mutual Automobile Insurance Company, its subsidiaries and affiliates (collectively “State Farm”). Nothing in the articles should be construed as an endorsement by State Farm of any non-State Farm product or service.
Breaking the Limits by Chad Prentice
Leveraging Cloud Architecture at Massive Scale

person taking photo with phone

As an insurance company, you’re bound to have a lot of documents to store and maintain. As a 100 year-old insurance company with over 87 million policies and accounts, State Farm REALLY has a lot of documents…to the tune of 12 billion documents weighing in at almost 3 petabytes of data. Those totals grow by more than 3 million documents (3 terabytes) a day. Think about an insurance claim for an auto accident. You have the photos of the damage, the estimate of the repair and the payment for…

READ MORE
Orchestrating Event-Driven Analytics with Ease by Evan Stalter & Tim Nickel

At State Farm our mission is to help more customers in more ways. To achieve that goal, a vast network of components across multiple platforms (PaaS, AWS, Salesforce, and Legacy to name a few) must flawlessly operate behind the scenes to help our agents and call center associates help new and existing customers. Much of this architecture today relies on synchronous point-to-point calls across these platforms, bringing potential challenges such as an outage that could negatively impact our daily…

READ MORE
Improving API Performance with HTTP Keepalive by Clete Blackwell II
Optimizing response time by reducing unnecessary connection reestablishment

Improving API Performance with HTTP Keepalive

Performance of business functionality is important. To keep this at the forefront, modern business functionality is backed by one or more customer-facing APIs (Application Programming Interfaces) which are often backed by a series of microservices. Any amount of unnecessary response time in a deeply-nested service can cause slow performance to customers, potentially creating inefficiencies and diminishing customer satisfaction.

READ MORE
Embracing Chaos by Ranjita Sahu
A Product Team's Journey

Perspectives

On a frigid night in late February 2012, I received a call for an emergency production issue. One of the critical batch jobs that processes data for the next day’s business had failed. At 9PM, there I was back in the office with 11 other State Farm developers. My then-product manager got us pizzas, coffee, and hot chocolate to cheer up the room, and the team spent the next couple hours pushing an emergency fix to production. Over the past decade, system failure analysis and maintenance…

READ MORE
L...A...T...E...N...C...Y by Ron Keane
We can't change the speed of light.

Clocks with lightning around them

Transitional architecture can be a challenge for companies as they plan their cloud journey. Migrating to the cloud typically means a piecemeal approach to moving applications and services. Applications and services that once existed in the same data center, are now hosted hundreds of miles from each other. Distance results in increased network latency.

READ MORE
AWS Multi-Account Management using Cloud Custodian and Serverless Compute by Ryan Ash
A simple and scalable approach to using Cloud Custodian for AWS governance, security and cost controls.

multi-tenant-cloud-custodian

Whether administering three or 300 AWS accounts, it is essential to implement consistent security and governance policies. Enabling users to leverage all the AWS services while remaining within the guardrails defined by your company is the goal. Polices should be relatively easy to create and implement. Having a stable deployment and runtime for these policies allows administrators to focus their valuable time elsewhere. Cloud Custodian policies provide flexibility to write governance rules in…

READ MORE