Tag: networks

Akamai vs Incapsula – Comparison Review

Application Delivery Controllers (ADCs) are the current evolution of old school CDNs platforms tasked with responsibility not only for website’s performance, but also for its security and availability. By singlehandedly covering these mission crucial aspects of content and application delivery these technologies allow you to replace multiple appliances with one full service solution. With that, ADCs help eliminate many integration related issues, while also dramatically cutting down all setup, acquisition and maintenance costs.

In the world of ADCs, Incapsula is perhaps the most promising up-and-comer, a cloud-based service that seems to have the technology and the business sense needed to position itself at the same level as its legacy competitors.

It’s been almost two years since I last blogged about Incapsula. Now with recent announcement of its load balancing and failover features, I decided to update my review by pitching Incapsula against Akamai – a globally recognized CDN industry leader, who is also making a leap into the world of full service application delivery.

For this “head to head” comparison of Akamai vs Incapsula, I’ll be focusing on security, performance, availability and – of course – price of service.

You can find the full comparison here but for those of you who want to skip to the chase, here’s what I think about in a nutshell:

Akamai vs Incapsula: In a Nutshell

Incapsula simply offers more for less. You get all of the essentials you would expect, including a robust CDN, PCI compliant Web Application Firewall, DDoS protection and integrated high availability features (both load balancing and failover), all at very reasonable price point.

Not only that, but when compared with Akamai it looks like most of Incapsula features actually offer more, both in terms of their functionality and in term of their overall synergy. One great example is Incapsula’s Real Time view which complements its custom security rules engine and load balancing features by providing instant feedback on every action taken.

In fact, when looking at value for money, Akamai does not offer any tangible benefits – at least not for those who are looking beyond a CDN-only option.

http2 explained

http2 explained – This document describes http2 at a technical and protocol level. Background, the protocol, the implementations and the future.

Some highlights:

  • The http2 spec is expected to ship in June 2014 (a month or two away!)
  • http2 is heavily based on Google’s SPDY
  • http2 is binary
  • http2 fixes a lot of issues with HTTP 1.1 (pipelining, head of line blocking, etc)
  • http2 brings new features (server push, block, reset)
  • http2 will keep the URL schemes (http and https)
  • http2 will mostly be implemented for https (via protocol negotiations in TLS)
  • http2 already has a variety of implementations: Firefox and Google Chrome (MSIE coming), cURL, Goolge, Twitter, Facebook.  Apache and Nginx expected.

The anternet

Stanford researchers discover the ‘anternet’

Transmission Control Protocol, or TCP, is an algorithm that manages data congestion on the Internet, and as such was integral in allowing the early web to scale up from a few dozen nodes to the billions in use today. Here’s how it works: As a source, A, transfers a file to a destination, B, the file is broken into numbered packets. When B receives each packet, it sends an acknowledgment, or an ack, to A, that the packet arrived.

This feedback loop allows TCP to run congestion avoidance: If acks return at a slower rate than the data was sent out, that indicates that there is little bandwidth available, and the source throttles data transmission down accordingly. If acks return quickly, the source boosts its transmission speed. The process determines how much bandwidth is available and throttles data transmission accordingly.

It turns out that harvester ants (Pogonomyrmex barbatus) behave nearly the same way when searching for food. Gordon has found that the rate at which harvester ants – which forage for seeds as individuals – leave the nest to search for food corresponds to food availability.

A forager won’t return to the nest until it finds food. If seeds are plentiful, foragers return faster, and more ants leave the nest to forage. If, however, ants begin returning empty handed, the search is slowed, and perhaps called off.

Prabhakar wrote an ant algorithm to predict foraging behavior depending on the amount of food – i.e., bandwidth – available. Gordon’s experiments manipulate the rate of forager return. Working with Stanford student Katie Dektar, they found that the TCP-influenced algorithm almost exactly matched the ant behavior found in Gordon’s experiments.