Section is a new class of content delivery network; built for agile teams.
Section believes there is no “one size fits all” approach when it comes to what software an engineer should choose for their application edge, or indeed on how many endpoints or where that application edge should exist. Section.io also believes that as more compute is taking place at the edge, software should be more reflective of an engineer’s application stack: fully-programmable, flexible, and easily adaptable.
Using Section, development teams can build web software with a binary equivalent of the production CDN running in their development environment. This, in turn, means developers can build applications that are CDN aware and where every app code deploy will work harmoniously with the configuration of the CDN. Ops teams can safely and reliably tune and configure the CDN in their local Dev environment to provide the maximum application performance and security improvement.
Supporting Continuous Integration and Continuous Deployment principles, Dev and Ops teams deploy Section's CDN using familiar Git commit processes. Section also provides real-time metrics and a logging platform (Graphite, Elasticsearch, Kibana, Logstash) providing teams with the same logs and metrics in Dev, Test, and Prod environments.
Section’s container-based approach to HTTP traffic delivery includes highly available and highly performant HTTP traffic control modules which can be run in a distributed fashion as a CDN and/or behind the firewall as an Application Delivery Controller.
Drupal contributions
We have created a module that integrates Drupal's Purge module with our distributed implementation of Varnish. It works with the cache tag purging that Drupal introduced in D8, and also can be used with any purge processor (like Purge's drush CLI) to purge any invalidation type (tag, url, domain, regex, etc)
