Welcome!

If everyone is thinking the same, someone isn't thinking

Lori MacVittie

Subscribe to Lori MacVittie: eMailAlertsEmail Alerts
Get Lori MacVittie via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Lori MacVittie

Scaling things seems like such a simple task, doesn’t it? Open a new checkout line. Call a new teller to the front. Hire another person. But under the covers in technology land, where networking standards rule the roost, it really isn’t as simple as just adding another “X”. Oh, we try to make it look that simple, but it’s not. Over the years we (as in the industry ‘we’) have come up with all sorts of interesting ways to scale systems and applications within the constraints that IP networking places upon us. One of those constraints is that physical (L2) and logical (L3) addresses have a one-to-one mapping. Oh, I know it looks like packets are routed based on IP address but really, they aren’t. They’re routed based on physical (MAC) addresses. And every switch (and router) keeps track of that mapping. 10.1.1.1? That goes to physical device A. 10.1.1.2? That goes to p... (more)

Management and Orchestration | @DevOpsSummit #DevOps #Microservices

Early (very early, in fact) in the rise of SDN there were many discussions around scalability. Not of the data plane, but of the control (management) plane. Key to this discussion was the rate at which SDN-enabled network devices, via OpenFlow, could perform “inserts”. That is, how many times per second/minute could the management plane make the changes necessary to adjust to the environment. It was this measurement that turned out to be problematic, with many well-respected networking pundits (respected because they are also professionals) noting that the 1000 inserts per secon... (more)

Ops Briefing: AMP HTML and Brotli By @LMacVittie | @DevOpsSummit #DevOps

I’m not going to start with a reminder of how important app performance is. Let’s just all agree we already know this as the first app economy axiom and get on with the post payload. Actually, I know this is true because I’ve watched a staggering increase in the past year in use of web acceleration services including techniques like compression. That’s why today’s ops briefing focuses on app performance and brings to your attention two emerging efforts (yes, both from Google, are you surprised?) designed to help you obey the first app economy axiom. AMP HTML The first one, AMP (A... (more)

Microservices, Service Registries, and Architectural Debt | @DevOpsSummit #DevOps #Microservices

Microservices is not just a style of application development, it’s a set of design principles guiding how applications are composed (or decomposed, as the case may be) with a resulting architectural shift as supporting components are added to the mix. Much in the same way SOA brought us UDDI registries and gateways, microservices is bringing service registries. Service registries, for the uninitiated, are kind of like the internal DNS of a microservices environment. They’re needed to manage the rapid association and disassociation with IP addresses of the containers in which the ... (more)

What Infrastructure Should Learn from NPM JavaScript Debacle By @LMacVittie | @DevOpsSummit #DevOps

If you hadn’t seen (and you might not have, it was a developer kind of thing after all) there was a big uproar caused by the removal of 11 lines of JavaScript from the popular NPM repository. You can read more about it but the TL;DR is this: dude removed some JavaScript that was relied on by thousands of other projects and basically broke them all. Because those projects not only relied on that code, but relied on code stored in an online repository. Now before we go further, I have to say that despite the millions (yes, millions) of projects that rely on JavaScript and CSS stor... (more)