When considering a vendor, one should stop and consider the underlying architecture of their product. Is it based on a sound foundation that has been proven and tested over time or is a collection of components that have been acquired over the years?
If properly designed, the architecture should serve as an important tool that aids your organization in the reasoning, analysis, and growth – not only for your current system(s) but also for your future requirements. In too many cases, organizations simply buy into a vendors Marketecture without taking the time to understand the basic philosophy and principles on which the system was designed.
It’s important to distinguish between a vendors Architecture and their Marketecture. Over the course of the next couple of weeks, we’ll ponder the differences and give examples of how you can separate fact from fiction in this space. In the mean time, I invite you to read about the War Ship Vasa http://hem.bredband.net/johava/WASAe.htm. This will be the case study that is used to highlight the effects of not having a sound architecture and the consequences of using a vendor who uses the terms Architecture and Marketecture in an interchangeable manner.
The study, conducted by Forrester Consulting, Inc. (NASDAQ: FORR), demonstrates that through the use of JUNOS Software and Juniper switches and routers, companies achieved an overall reduction in operational costs for specific network operations tasks, including planning and provision, deployment, planned and unplanned network events.
Among other top-line results, the study reports a 41% reduction in overall network operations costs based on dollar savings across specific task categories: planned events, reduction in frequency and duration of unplanned network events, the sum of planned and unplanned events, the time needed to resolve unplanned network events and the “adding infrastructure” task. The study also reveals:
* 54% reduction in maintenance and support costs (a “planned events” category)
* 27% reduction in network downtime (based on reduction in frequency and duration of unplanned network events)
* 41% increase in network stability/reliability (the sum of planned and unplanned events)
* 40% decrease in time to resolution (the time needed to resolve unplanned network events)
* 25% reduction in cost to deploy (the “adding infrastructure” task)
Junos demonstrates the power of one operating system to reduce complexity. Read the complete report at http://www.juniper.net/us/en/company/press-center/press-releases/2009/pr_2009_02_24-08_02.html and stay tuned for more news about how you can leverage Junos to program the new network.
Ask any server administrator how easy it is to manage Windows, Linux, Unix, and mainframe OSes all at the same time. Chances are they will spend hours telling you about lost productivity, frustrated end users and in many cases lost revenue. Unfortunately, most network operations teams face that exact challenge if they’re running two to three vendors throughout their environment. This is the reason that we are taking at different approach at Juniper Networks with Junos. One open NOS that spans all of our devices. Over the course of the next several months, we’ll be discussing how developers can take advantage of our unique approach and leverage the network to build compelling new applications. If you are interested in learning more about what we are doing – start here with this study from Forrester http://www.juniper.net/us/en/reports/single_network_os.pdf.