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)
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)
It was a Monday. I was reading the Internet. Okay, I was skimming feeds.
Anyway, I happened across a title that intrigued me, "Stateful Apps and
Containers: Squaring the Circle." It had all the right buzzwords (containers)
and mentioned state, a topic near and dear to this application
networking-oriented gal, so I happily clicked on through.
Turns out that Stateful Apps are not Stateful Apps. Seriously.
To be fair, I should really say that when a devops guy talks about
‘stateful apps' it is not the same thing as when a netops gal uses the term
‘stateful apps.' That's because the... (more)
Your car. My toaster. Our lights. The neighbor’s thermostat.
With an average of 7.8 connected devices per home, according to recent
surveys, there are twice as many “things” in the house as the average
3.14 people per household in the US in 2015.
And all of them are “talking.” Not all talk to each other, yet, though
the foundation for that is clearly laid out. But all of them talk to apps
which talk to them over the Internet.
When you or I interact with that app, we do so via HTTP (hopefully secured).
Whether it’s via a native mobile app that uses APIs or a modern web app is
Yes, Lori has been reading the Internet again. And what she's been seeing
makes baby Lori angry. It also makes this former test designer and technology
editor cry. Really, I weep at both the excuses offered for such testing and
the misleading headline.
I have read no less than two contrived comparisons of "HTTPS" and "HTTP" in
the last two weeks purporting to demonstrate that secure HTTP is inarguably
faster than its plaintext counterpart, HTTP.
Oh, if only that were true.
See, the trick is that both comparisons (and no doubt many more will follow)
are comparing secure HTTP/2 wi... (more)