The Impact of the Observer Effect on Microservices Architecture
Application availability is not just the measure of "being up". Many apps can
claim that status. Technically they are running and responding to requests,
but at a rate which users would certainly interpret as being down. That's
because excessive load times can (and will be) interpreted as "not
available." That's why it's important to view ensuring application
availability as requiring attention to all its composite parts: scalability,
performance, and security.
The paradox begins when we consider how we ensure scale, performance, and
security: monitoring and measuring. That is, we observe certain
characteristics about the network, compute, and application resources to gain
an understanding of the status of the application. That necessarily means we
have to interact with those components that need monito... (more)
DevOps Summit: Where the Network Got Invited to the Party
At DevOps Summit NY there's been a whole lot of talk about not just DevOps,
but containers, IoT, and microservices. Sessions focused not just on the
cultural shift needed to grow at scale with a DevOps approach, but also made
sure to include the network "plumbing" needed to ensure success as
applications decompose into the microservice architectures enabling rapid
growth and support for the Internet of (Every)Things.
Containers and Microservices and the Network
Jerome Petazzo (@jpetazzo) of Docker discussed microservices and... (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)
Can you use both? Of course you can! Here comes the (computer) science…
One of the big performance benefits of moving to HTTP/2 comes from its
extensive use of multiplexing. For the uninitiated, multiplexing is the
practice of reusing a single TCP connection for multiple HTTP requests and
responses. See, in the old days (HTTP/1), a request/response pair required
its own special TCP connection. That ultimately resulted in the TCP
connection per host limits imposed on browsers and, because web sites today
are comprised of an average of 86 or more individual objects each needing its ... (more)
Programmability in the Network: Risk-based Data Scrubbing
This post is brought to you by the letter “C” (for context).
There’s a whole lot of talking and proposing and presenting going on around
risk-based. Usually it’s around authentication and access. The basic
premise is that based on a score, formulated from a set of variables
(context), you decide whether or not someone is allowed access to a resource.
The formula is based on context and can include things like location, device,
time of day, day of week, and application status.
Now, interestingly enough, one of the top five s... (more)