We’re excited to be at Velocity Santa Clara this week (June 24-26) to talk about the future of web performance, meet new people, and participate in a few offsite events!

Streaming logs is one of our most popular features. It's fast and flexible, giving operations teams more data from the edge than ever before and in real time. Since its release, we've seen Fastly customers use some cool tricks in configuring their log streams for a wide variety of use cases, and we wanted to share some tips.

With Fastly, you have the freedom and flexibility to completely customize your caching settings. From respecting Cache-Control headers sent from your origin servers to allowing you to granularly set rules for any object or set of objects that flow through the CDN, we give you full control.

We’re always looking for ways to make it easier to integrate with Fastly. Recently, we’ve targeted a few high-profile frameworks, such as Ruby on Rails, and built plugins for them. This week, we’re happy to announce the latest plugin in our growing library: the Fastly Drupal 7 Module.

At April's WebPerf meetup in San Francisco, Fastly Chief Performance Officer Steve Souders discussed the synchronous and asynchronous nature of Web Components, and how they can impact the rendering of the entire page.

Fastly principal engineer Jason Cook explains how he uses iPXE and Chef to get to boot management bliss. Check out his slides from ChefConf 2014 here.

 

 

Fastly is a developer-minded CDN, so we're always looking for ways to integrate with the most popular frameworks and platforms. Today, we're happy to announce a number of improvements aimed at the Ruby on Rails community.

Today, Fastly principal engineer Jason Cook will be speaking at ChefConf 2014 in San Francisco. His talk will focus on building a boot system using Chef's API and iPXE to create a lightweight tool for managing install and firmware updating of hosts and network gear.

Here’s the latest update on the ongoing resolution to critical OpenSSL vulnerability CVE-2014-0160, aka 'Heartbleed,' which was announced on April 7th and affects nearly every Internet service provider and website using SSL to secure customer traffic.

This week, we’re traveling to Montreal for PyCon 2014. If you’ll be there, make sure to stop by booth #611 in the Exhibit Hall to chat with a Fastly engineer, explore our real-time analytics dashboard, and pick up a Fastly shirt.

We were thrilled to be a part of Fluent Conf 2014. Big thanks to everyone who stopped by the Fastly booth to chat with our engineers and pick up a Fastly shirt.

If you missed Fastly CPO Steve Souders' Fluent talk about the Perception of Speed, you can watch it below.

The Fastly team is attending Fluent this week in San Francisco. We’ll be at booth #206 right next to our friends from New Relic. Come by to talk with one of our engineers, grab a Fastly shirt, and learn how to win our DevOps survival kit.

Today, we’re excited to welcome three new Fastly team members.

In this, our final API Caching installment, we're going to explore how to use Surrogate Keys to reduce the overall complexity of caching an API.

At Fastly, we’re always working to make our systems faster and more reliable. One of the more difficult problems we’ve faced is efficient cache invalidation across our global network, or as we call it: Instant Purging. When content changes, our customers issue a purge request, which we then need to deliver to each of our cache servers. The system that handles these purge requests is codenamed Powderhorn.

Why fiber routes, eyeball networks, and growth forecasting, not just population, determine where Fastly places new points of presence on its edge network.

In Part 1, we covered the basics of using Fastly to accelerate a comments API. Using Instant Purge, we hooked into model callbacks to ensure that the appropriate content was purged from the cache whenever data changed. In this article, we’ll build upon the original approach and use one of Fastly’s more advanced features: cache control.

Over the last few months, we’ve completely overhauled Fastly’s entire logging infrastructure to keep up with our ever-increasing traffic. In addition to improving efficiency and reliability, we added features to make it easier for our customers to integrate with the logging providers they already use.