Let’s start by answering a simple question: which social media services do you use?
- All of the above
In 2012 OpenFlow discussions turned into SDN ones. Related although different in significant ways, both OpenFlow and SDN drove a significant level of attention in the networking industry as Nicira’s Acquisition and Cisco’s moves served to establish the commercial value of SDN. In 2013, we are witnessing serious momentum in terms of discussions and start-ups around SDN. However, the questions remain as to which solutions will be successful and which solutions will become available in the market place first?read more
As the industry and the media keep feeding the Software-Defined Networking (SDN) hype and vendors introduce SDN products into the market – it is becoming increasingly important to understand the difference between various offerings as well as the ways in which they can help end users.
The majority of the discussion has centered on changes in forwarding functionality – the functionality of forwarding packets between interconnection ports of networking devices. With OpenFlow (which is not SDN, but is what triggered a lot of the SDN discussion) the intelligence making the forwarding decisions, which lies in the control plane, has moved out of the forwarding platforms that connect the external systems into the network and into the controllers. Here we have decoupled OpenFlow switches and controllers.
This post is part one of a three part series in response to the three major challenges related to SAP infrastructure articulated by professionals at TechEd
At the recent SAP TechEd conference in Las Vegas the theme from end-users was the same. From C-level executives and directors to everyday technology professionals, we heard the following concerns voiced again and again:
- Quality of experience is a huge issue when it comes to managing the latency of my organization’s SAP applications.
- I need to guarantee business continuity at all times.
- I need to ensure my SAP Applications are secure.
To be sure, the major challenge derives from the fact that SAP applications serve as mission critical infrastructure for the mainstream business processes that most end users touch throughout their day. SAP applications are designed to provide advanced business functionality to help organizations efficiently meet their business goals. Any SAP deployment counts on network and server infrastructure performance and availability as well as the ability to protect the deployment from malicious network and application attacks. In addition, SAP deployment is also dependent upon the ability to scale and support multiple applications and types of users, and all of this while being cost effective as well.
The devastation wrought by superstorm Sandy is a stark reminder of just how fragile our environment is versus the power of nature. In just a couple of days, a single storm disrupted the lives of so many people and paralyzed a large number of businesses even days after it passed. In the wake of the storm, one of the questions on my mind is, how can we help businesses remain functional after such a massive hit regardless of their size?
Working for an Application Delivery Controller company, I’m no stranger to disaster recovery. Most often, disaster recovery is initiated by large enterprises that invest big money to build entire backup datacenters with the ability to automatically provide all online services in case their main datacenters become unavailable. A reality faced by many businesses in and around New York after the storm.
Written by: Meryl Robin, Director of Virtual Solutions, Radware Inc and Yaron Azerual, Product Marketing Manager, Radware Inc.
The challenges of application slowdown: Identify where the slowdown occurs and why. Give your users unmatched QoE and routinely meet the highest level of SLA
We should discuss what the main goal for deploying an ADC is: 95% of the time, it is to enforce increasingly more stringent application SLA’s. To achieve this, we have to consider improving application availability, whether you’re solving local server failure with local server load balancing or fixing global downtime through GSLB with a DR site. It’s also important to improve performance by offloading some of the CPU intensive tasks from the server to the ADC, like SSL, compression, or even smart caching (dynamic caching for even faster response time of the application).read more