KML_FLASHEMBED_PROCESS_SCRIPT_CALLS

Posts Tagged ‘Dynamic Load Balancer’

 

How Software Defined Networking Delivers Next-Generation Success

Wednesday, June 5th, 2013 by

Software defined networking (SDN) is today where the cloud was a few years ago, and their paths are quite similar. As cloud providers innovate, they incorporate new, cutting-edge technology to let users do more with their architectures and enable solutions that were previously impossible. Just as the cloud moved people away from physical boxes and bare metal devices, SDN is allowing developers and architects to divorce themselves from proprietary hardware appliances like load balancers and firewalls.

So, what are the similarities between SDN and cloud? How about abstraction or the movement from physical to virtual?

To get a bit more scientific, I jumped over to Google Trends (which looks at search term volume over time) and did a search for “cloud,” “SDN,” “cloud computing,” and “software defined networking.”

cloud-sdn-trends

The results shown here make it pretty obvious that “cloud” continues to grow and overshadow the other terms. Removing “cloud” shows “SDN” making the same upward trajectory as “cloud” does in the graphic below. (Because people have been shortening the term “cloud computing” to simply “cloud,” it’s logical that the term’s search volume is decreasing.)

snd-cloud-comp-software-defined-network-trends

(more…) «How Software Defined Networking Delivers Next-Generation Success»

Is Your High-Tech Company Ready For An SDN-Enabled Cloud?

Thursday, April 18th, 2013 by

When it comes to technology, there are many companies on the “bleeding edge” these days. Sometimes these companies achieve greatness by being visionary, producing products or services that others haven’t thought of, or investing heavily in R&D. But they all have one thing in common: They use the latest high-tech, innovative solutions to power their journeys.

image

When it comes to the underlying infrastructure powering a technology-oriented company, “cutting edge” means success. Sites and services need to perform, be reliable, be resilient, and have the flexibility to expand and contract based on the ebb and flow of day-to-day business. For me, that means cloud infrastructure is the best solution for companies looking to stay ahead of the curve.

Over the past few months, GoGrid has released a variety of services and features designed to give companies a leg up on the competition. It’s all centered on providing cloud infrastructure that’s flexible, yet forward-thinking. It’s much more than simply needing faster and bigger clouds—it’s about architecting our cloud solutions to provide customers with a highly available and distributed set of infrastructure components. And it’s architected according to software-defined networking (SDN) concepts.

SDN architecture isn’t focused on internetworked commodity hardware or new ways to provide networking services. It’s designed to distribute a variety of formerly hardware-based solutions across nodes, data centers, and clouds. When you think about “old school” infrastructure architecture, you probably think of physical devices. And if you think about one device, you really need to think about two, for redundancy and backup. If your hardware load balancer or firewall fails, you have to be sure you have a warm or hot standby available to immediately take its place. That requires time and money. And if you want to be cutting edge, you don’t want to be spending your precious time and money planning for the inevitable. You want to be innovating and iterating.

That’s where SDN is truly powerful and why many of the leading technology companies are adopting solutions that use it. With SDN, you can build in fault tolerance and redundancy. Take our recently released Dynamic Load Balancers as an example. Instead of relying on a single hardware device for routing traffic between available servers, our Dynamic Load Balancers are distributed and highly available across our Public Cloud. If one of the Dynamic Load Balancers fails, another instance, complete with configurations, is spawned immediately elsewhere thanks to our self-healing design. And these load-balancing services can be controlled programmatically via our API.

This month we announced another service that operates in the same distributed manner, our Firewall Service. Although many companies choose to use Cisco ASAs as a security front end for their cloud and physical infrastructure environments (an offering we also provide), these are physical devices that require management. However, our SDN architecture lets us provide more resilient and creative solutions. Like our Dynamic Load Balancers, our Firewall Service is built around SDN concepts and distributed across nodes and our data centers. When you create a security group (that has policies assigned to it), it’s automatically replicated across all our data centers within seconds. If you have distributed infrastructure, you can simply assign a security group to any similarly configured Cloud Server, regardless of that server’s location. If you subsequently change a policy, it’s automatically synchronized to all servers across all data centers that are part of that security group. In other words, you configure once, assign the security group to the server(s), and then watch the SDN magic happen.

(more…) «Is Your High-Tech Company Ready For An SDN-Enabled Cloud?»

How To Create a Distributed, Reliable, & Fault-Tolerant GoGrid Dynamic Load Balancer

Tuesday, February 26th, 2013 by

As Rupert Tagnipes outlined in his article “High Availability with Dynamic Load Balancers,” crafting a fault-tolerant, reliable website is critical to a company’s online success. There’s nothing worse than going to a website to do a transaction only to have it either be slow to respond or have an interaction time out. By setting up a load balancer in front of transactional web or application servers, companies can ensure their web presence is resilient, responsive, and gets information to their customers reliably.

image

GoGrid launched with a free load-balancing service in 2008. This year, we introduced our next-generation cloud load-balancing service on GoGrid. Embracing the software-defined networking (SDN) mantra, we created our load-balancing service to embrace the key characteristics of cloud computing: on-demand, usage-based, and distributed. I encourage you to read more about our Dynamic Load-Balancing service in Rupert’s article.

Although understanding why load balancing is critical to success is important, knowing how to create a new GoGrid Dynamic Load Balancer is equally important. This How-To article will guide you quickly and easily down that path.

Dynamic-load-Balancer

As always, I like to boil the process down to 3 easy steps. In the case of the Dynamic Load Balancer creation process, these steps are:

(more…) «How To Create a Distributed, Reliable, & Fault-Tolerant GoGrid Dynamic Load Balancer»

High Availability with Dynamic Load Balancers

Monday, February 4th, 2013 by

Building out a highly available website means that it is fault-tolerant and reliable. A best practice is to put your web servers behind a load balancer not only to distribute load, but also to mitigate the risk of an end user accessing a failing web server. However, traditional load balancing funnels traffic into a single-tenant environment—a single point of failure. A better practice is to have a distributed load balancer that takes advantage of the features of the cloud and increases the fault-tolerance abilities on the load balancer. GoGrid’s Dynamic Load Balancer service is designed around a software-defined networking (SDN) architecture that turns the data center into one big load balancer.

traffic_light_2

GoGrid’s Dynamic Load Balancer offers many features, but one of its core features is high availability (HA). It is HA in two ways.

First, on the real server side, deploying multiple clones of your real servers is a standard load-balancing practice. That way, if one of your servers goes down, the load balancer will use the remaining servers in the pool to continue to serve up content. In addition, each GoGrid cloud server that you deploy as a web server (in the real server pool) is most likely on a different physical node. This setup provides additional protection in the case of hardware failure.

Second, on the Dynamic Load Balancer side, the load balancers are designed to be self-healing. In case of a hardware failure, Dynamic Load Balancing is designed to immediately recover to a functioning node. The Virtual IP address of the Dynamic Load Balancer (the VIP) is maintained as well as all the configurations, with all the changes happening on the back end. This approach ensures the Dynamic Load Balancer will continue to function with minimal interruption, preventing the Dynamic Load Balancer from being a single point of failure. Because the load balancer is the public-facing side of a web server, whenever it goes down the website goes down. Having a self-healing load balancer therefore makes the web application more resilient.

Users with websites or applications that need to always be available would benefit from including GoGrid’s Dynamic Load Balancing in their infrastructure. The load balancer is important for ensuring the public side of a service is always available; however, including easily scalable cloud servers, the ability to store images of those servers in persistent storage, and the option to replicate infrastructure between data centers with CloudLink are all important elements of a successful HA setup.

(more…) «High Availability with Dynamic Load Balancers»