Chris McFadden, Author at SparkPost

Posts by Chris:

Feb. 21, 2018 by C. McFadden

4 Questions to Ask Before Migrating Your App or Service to the Cloud

Cloud migration involves major changes to business processes and company culture. Here are four questions you should ask before embarking on this adventure.

Dec. 8, 2017 by C. McFadden

How to Use Microservices to Build an API That Lasts

Learn some successful strategies we use to build our microservices architecture and how they allow us to evolve our API during rapid growth.

Aug. 30, 2017 by C. McFadden

Upcoming API Transmission Endpoint Changes

We’re making some API Transmission Endpoint changes. Learn how the changes will improve performance and optimize end-to-end delivery latency.

Jun. 7, 2017 by C. McFadden

Operating DNS on the AWS Network: Challenges and Lessons

Learn how our team worked with AWS to address a challenging DNS performance issue—and tips for troubleshooting with the AWS support team.

May. 24, 2017 by C. McFadden

RESTful API Versioning Best Practices: Why v1 is #1

Breaking changes can result in frustration and loss of trust between an API provider and their users. API versioning is one way to avoid that frustration.

May. 3, 2017 by C. McFadden

Configuration Management and Provisioning in AWS with CloudFormation, Ansible, and Puppet

Experimenting with various configuration management and provisioning tools taught our teams how important it is to not get too attached to specific tools.

Mar. 15, 2017 by C. McFadden

SparkPost Labs: A/B Test API

Our VP of Engineering introduces SparkPost Labs. Learn how we're sharing new and experimental API and App functionality with our developer community.

Feb. 15, 2017 by C. McFadden

Our DevOps Journey: Focusing on Deployment Automation

Concluding our devops journey series, Chris shares some of what we have in store for this year as we focus on improved deployment automation.

Feb. 7, 2017 by C. McFadden

The Day Our DNS Hit an Undocumented Limit in AWS

Learn what happened when we ran into—and solved—an unusual condition in Amazon Web Services (AWS) that impacted our DNS infrastructure and our service.

Chris McFadden