At our second annual customer summit, Andrew Betts of the Financial Times discussed using VCL to “solve anything” — pushing his team’s problems to the CDN layer.

In this post, Tyler McMullen will explore “the future of the edge,” or the next logical step in how we streamline online experiences. In order to keep up with the direction things are headed, we need to combine logic and data at the edge. Logic without data, without state, is insufficient.

We hosted our first-ever customer summit in June of last year, with the goal of bringing together our customers and the people who build our products to discuss web performance, Varnish, and the future of Fastly. Systems Engineer Ines Sombra’s Altitude 2015 talk, “The fallacy of fast,” reflects on the shortcuts we tend to take when we iterate quickly.

The popularity of implementing microservices in today’s application landscape continues to rise. There have been countless success stories focused on migrating from a monolithic architecture (a single large application stored in one code repository) to microservices, in which parts of application logic are broken into smaller functional services.

We’re continuing to build on our unique ability to push your logic and decisions to the edge, and are happy to announce some exciting enhancements to our Edge Dictionaries. Our latest improvements include Upsert functionality as well as the ability to make bulk updates and issue patch commands.

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.

Customer Support Engineer Kami Richey built an application for testing Fastly. In this post, she walks you through setting up your own test application and using Fastly’s UI to explore commonly used features first hand.

In this Q&A, Fastly’s Michael May and Heroku’s Peter Cho discuss the benefits of Fastly’s Heroku add-on and why it’s important for enterprises to focus on both developer and customer experiences.

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

Before diving into CORS (Cross-origin resource sharing), I need to mention JSONP, which is the other solution to getting data from a different “Origin.” In Using ESI, Part 2: Leveraging VCL and ESI to Use JSONP, Simon explains what JSONP is, and how to cache it with Fastly, using one Fastly specific feature, req.topurl. Now, with Varnish 4.1, req.top.url (note the extra period) is available, and it allows you to do the same thing with vanilla Varnish.

It’s difficult to change course mid-career and educate yourself on a new subject after college has ended. For those entering the field of engineering, it often means taking coding classes or taking part in a coding bootcamp, such as those offered at App Academy, General Assembly, Hackbright Academy, and Hack Reactor.

We had the opportunity to sit down with Miles Ward and chat about trends in the cloud industry, working with Fastly, and how Google Cloud Platform really sets itself apart.

This month's tip is more a theoretical exercise than anything else, just to show the power of VCL, and to explain a few regular expressions. I'm going to discuss VCL that deletes cookies.

In November 2014, we announced Fastly’s Cloud Accelerator, a collaboration with Google Cloud Platform that combines the power of Google’s infrastructure with the speed and flexibility of our real-time content delivery network. We're seeing more of our customers leverage cost-effective cloud services to build scalable infrastructure, and so today we're excited to announce that we're expanding our collaboration with Google Cloud Platform.

Reusing connections between your Varnish instance and your backends (origins) is a good idea for multiple reasons. If your Varnish is on the same network as your backends and you're doing low volume traffic, you can stop reading, because a) the difference will probably be negligible, and b) you're probably already reusing backend connections.

Moving to a new content delivery network (CDN) can seem daunting from an operational standpoint, and it’s important to ensure your CDN is set up correctly before you start migrating all your traffic. In this post, I’ll outline a few steps you can take to experience a smooth migration process to Fastly.

Varnish is an open source web accelerator that is designed for high-performance content delivery. Learn more about what Varnish is and how Fastly's varnish can help accelerate your content.

The cache hit ratio (or hit ratio for short) is the ratio of hits to cacheable requests (hits and misses combined). There's also cache coverage, the ratio of cacheable requests to all requests (cacheable requests and passes). In most cases, you'll want both to be as high as possible, since misses and passes cause load on your origins, and are slower than cache hits.

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.