Wait, what is the title of this blog post and what does it mean? Well as you are probably aware, Cisco Live 2016 is just a few months away from now – in fact just about 90 days from now! So around this time when information starts to come out as to who we may […]
The post Cisco Live 2016 – Animals and Oh’s! appeared first on Fryguy's Blog.
Google writes a book on data center reliability.
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
The cloud is the promised land when it comes to storage. A recent 451 Research report said AWS and Azure will be two of the top five enterprise storage vendors by 2017 with AWS as number two overall. But the challenge with using the cloud for primary storage is the latency between that storage and users/applications. To take advantage of the economics, scale, and durability of cloud storage, it will take a combination of caching, global deduplication, security, and global file locking to provide cloud storage with the performance and features organizations require.
To read this article in full or to leave a comment, please click here
Forget the analyst hand-waving. Customers like immediate benefits.
Although vendor-written, this contributed piece does not promote a product or service and has been edited and approved by Network World editors.
I’m an aerospace engineer by degree and an IT executive by practice. Early in my career, I worked on missile hardware and simulators with some of the smartest minds at Marshall Space Flight Center in Huntsville, AL. An adage from those days still drives me today: “Better is the evil of good enough.”
In rocket science, an astronaut’s life is literally in the balance with every engineering decision. Being perfect is mission critical. But along the way, NASA engineers realized while perfection is important, it was not to be universally adopted, for several key reasons: It is very expensive, it draws out timelines, and it can result in extreme over-engineering.
To read this article in full or to leave a comment, please click here
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
Only 1% of companies use software-defined WAN (SD-WAN) solutions today, but Gartner says the promise of cost savings and performance improvements will drive that number to more than 30% by 2019. Why aren’t more businesses deploying now given the sizeable list of vendor tools available? It could be a lack of understanding about the varying approaches to bringing software-defined networking to the branch.
Before exploring those differences, let’s review why SD-WAN is so promising for branch environments. Compared to traditional WANs, SD-WANs reduce the complexity of network hardware at branch offices and centralize and simplify management. SD-WANs also allow businesses to augment or replace MPLS networks by using less expensive Internet links in a logical overlay and intelligently routing traffic over multiple paths directly to the Internet, rather than through a central data center. This improves application performance and makes more efficient use of bandwidth.
To read this article in full or to leave a comment, please click here
Before talking the final point in the network design mindset, ,act, I wanted to answer an excellent question from the comments from the last post in this series: what is surface?
The concept of interaction surfaces is difficult to grasp primarily because it covers such a wide array of ideas. Let me try to clarify by giving a specific example. Assume you have a single function that—
This single function can be considered a subsystem in some larger system. Now assume you break this single function into two functions, one of which does the addition, and the other of which does the multiplication. You’ve created two simpler functions (each one only does one thing), but you’ve created an interaction surface between the two functions—you’ve created two interacting subsystems within the system where there only used to be one. This is a really simple example, I know, but consider a few more that might help.
We collect the top expert content in the infrastructure industry and fire it along the priority queue.
Hey, it's HighScalability time:
