There’s a tendency, particularly for networkers, to classify applications
by the protocols they use. If it uses HTTP, it must be a web app. The thing
is that HTTP has become what it was intended to be: a transport protocol. It
is not an application protocol, in the sense that it defines application
messages and states. It merely transports data in a very specific way.
That’s particularly important in the age of the API and, increasingly, the
age of things that might be using APIs. You see, APIs are primarily data
centric constructs while web pages (think any HTML-based app) are document
Data centric constructs tend to exchange, well, data. And document centric
constructs… yes, exchange documents. Both might use HTTP as a mechanism to
do that, but the actual payload carried differs dramatically. That’s
because data centric constructs are concerned... (more)
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)
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
Microservices versus Microsegmentation
Let's just nip the conflation of these terms in the bud, shall we?
"MIcro" is big these days. Both microservices and microsegmentation are
having and will continue to have an impact on data center architecture, but
not necessarily for the same reasons. There's a growing trend in which folks
- particularly those with a network background - conflate the two and use
them to mean the same thing.
They are not.
One is about the application. The other, the network. There is a
relationship, but it's a voluntary one. They are two very different thing... (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)