We’re pleased to announce we now support log streaming to Google Cloud Storage (GCS) endpoints. Fastly’s GCS support strengthens our existing Log Streaming capabilities for common endpoints.

Sales Engineer Léon Brocard created fastly2git, a Git repository for Fastly service changes, making it easy for you to see differences between versions. In this post, Léon discusses how fastly2git works, and how it can help you continue building great services on Fastly.

We’re always seeking ways to give our customers more control at the edge. With this in mind, we’re excited to announce Edge Dictionaries, which give you the ability to create readable key/value pairs using our API.

In this blog post, Vladimir Vuksan outlines three common methods you can use for blocking or limiting access to content with Fastly.

We often say that Fastly can easily become an extension of your app — there are three major components that make this possible: caching, control, and visibility.

We’re more engaged online than ever before, especially when it comes to consuming news. If you work with online media brands, you’re well aware that the way readers engage with news events is changing.

You may not know that the software your developers use can affect the success of your marketing activities. It’s within both teams’ interests to collaborate to ensure good performance.

In a previous post, I discussed the benefits of Fastly edge modules. Among those listed is GeoIP / Geography Detection, which is useful for any company (especially those in ecommerce, hospitality/travel, and media) that needs to segment content delivery based on geographic location.

Ecommerce companies face challenges that a content delivery network built on Varnish can help address. To stay competitive and relevant, ecommerce websites and applications need to be able to target specific content to specific users (based on location, language, or browsing preferences), tailor content delivery depending on which device a consumer is using, and prioritize shoppers based on actions they’ve taken within a site or app.

If you want to increase the efficiency of your Varnish (or Fastly) cache, you need to figure out what traffic is not cached. By definition, any traffic that reaches your origin is not cached, and thus worthy of investigation.