I am often humbled by the depth of insight of those who toil in the trenches
of the enterprise data center.
At our Agility conference back in August, my cohort and I gave a presentation
on the State of Application Delivery. One of the interesting tidbits of data
we offered was that, over the course of the past year, our iHealth data shows
a steady and nearly even split of HTTP and HTTPS traffic. To give you an
example, my data from October was derived from over 3 million (3, 087, 211 to
be precise) virtual servers. Of those, roughly 32% were configured to support
HTTP, and another 30% were supporting HTTPS.
Now, I’ve been looking at this data for more than a year, and it has stayed
roughly the same with only slight variations up or down, but always within a
couple percentage points of each other. But it wasn’t until a particularly
astute customer spoke up that I un... (more)
JANUARY 8, 2014 02:00 PM EST
When we talk about the impact of BYOD and BYOA and the Internet of Things, we
often focus on the impact on data center architectures. That's because there
will be an increasing need for authentication, for access control, for
security, for application delivery as the number of potential endpoints
(clients, devices, things) increases. That means scale in the data center.
What we gloss over, what we skip, is that before any of these "things" ever
makes a request to access an application it had to execute a DNS query.
Every. Single. Thing.
Maybe that's ... (more)
In case you haven’t heard, the new hotness in app architectures is
serverless. Mainly restricted to cloud environments (Amazon Lambda, Google
Cloud Functions, Microsoft Azure Functions) the general concept is that you
don’t have to worry about anything but the small snippets of code
(functions) you write to do something when something happens. That’s an
event-driven model, by the way, that should be very familiar to anyone who
has taken advantage of a programmable proxy to do app or API routing and
rewriting or executed inspection of requests or responses for malicious
I've been reading up on APIs cause, coolness. And in particular I really
enjoyed reading Best Practices for Designing a Pragmatic RESTful API because
it had a lot of really good information and advice.
And then I got to the part about compressing your APIs.
Before we go too far let me first say I'm not saying you shouldn't compress
your API or app responses. You probably should. What I am saying is that
where you compress data and when are important considerations.
That's because generally speaking no one has put their web server (which is
ultimately what tends to serve up respons... (more)
It's all about that architecture.
There's a lot of things we do to improve the performance of web and mobile
applications. We use caching. We use compression. We offload security (SSL
and TLS) to a proxy with greater compute capacity.
We apply image optimization and minification to content.
We do all that because performance is king. Failure to perform can be, for
many businesses, equivalent to an outage with increased abandonment rates and
angry customers taking to the Internet to express their extreme displeasure.
The recently official HTTP/2 specification takes performance very... (more)