The Importance of Licensing to Equalize Dev and Production
We’re all aware that dev/test != production environments. While the
software stacks upon which applications are deployed may be (and hopefully
are) the same, there still remains a whole lot of “infrastructure”
(that’s everything else) that isn’t the same. Routers, switches, security
devices, load balancers, caches, and other devices dedicated to ensuring the
secure delivery of applications to hungry consumer and corporate users simply
don’t exist in the dev/test environment. That’s particularly true as
organizations continue to view “the cloud” as its ideal dev/test
environment while continuing to insist that production remain firmly rooted
The State of the Developer Nation Q3 2015 from VisionMobile noted this
phenomenon: Almost half of developers are hosting their apps in private
clouds, well... (more)
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 anot... (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)
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 do... (more)
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)