Unstructured Data: Cloud to the Rescue… Right?

One way to overcome a lot of the previously mentioned challenges and concerns with storing such large amounts of unstructured data is to move it to a public cloud provider. As for the previously discussed challenges of legacy NAS filers, most of those concerns would no longer be applicable. Essentially, you would be paying the cloud provider to worry about all the infrastructure concerns like capacity, performance, uptime, H/W support, and so on.

While washing our hands at a sink, do we think about the source of that water… or do we just expect it to be there when we turn it on? Do we set hot, warm, or cold temperatures according to our unique comfort levels?

Performance, Capacity, Scalability, Availability, Security, and Recoverability: These are all pillars of a multi-cloud data center strategy. In the past, applications were dependent on the on-premises data center infrastructure. “What you see is what you get” was pretty much how application developers had to deal with it. Today, the business dictates how an organization deploys data center resources to support an application. For a commercial business, the desire is for the application to generate significantly large amounts of data traffic that translates into revenue. For the public sector, it’s about getting information to and from the community at a rapid pace.

I was recently asked by a colleague to build a portal to allow engineers to start and stop two Amazon EC2 instances that host software used for network discovery and mapping. The intent was to only have them running when necessary to reduce the cost of instances running when they are not in use.  Jokingly, I asked if he wanted me to build this portal on an EC2 instance. He didn’t catch the joke, so I explained that running one full-time instance to control two other instances was probably not going to be very effective at saving money.

Many of the customers I interact with have on-premises data centers, and they swear that they will never go to the cloud. On the other side of the spectrum, some customers have fully embraced cloud, to the point where they are running all their workloads in the cloud. In the middle, I have customers who are running some applications in the cloud and some on-premises—a hybrid environment, if you will. As a Solutions Architect, I feel the need to expand on why organizations choose between these varying architectures when designing their data center.

A business process outsourcing (BPO) provider with 5,000 global agents was primarily focused on customer experience and contact center outsourcing for large companies. Like many in its industry, the BPO ran on very tight margins and wanted to move away from spending capital money. It preferred operational expenses because it billed its customers on a monthly usage basis (i.e., how many phone calls it took), so it desired to match its cost structure with its revenue structure. Having to pay money upfront with the hope that the customers would use the system would not benefit the BPO; instead, it desired for its underlying technology and business costs to be paid when its clients made payments. For this reason, an “As-a-Service” model best suited the BPO from a financial and technology perspective.

I recently had a meaningful conversation with a customer as we spoke of a three-year plan to move “everything” into the cloud. I hear this statement over and over again, and it always brings visions to my mind of jumping into the deep end of the pool without knowing how to swim. For most, the perception is that the cloud provides a robust data center for multiple use cases—anywhere from dev, test, disaster recovery, and, of course, production workloads. Organizations look to the cloud as a way to solve their challenges in operating on-premises primary, secondary, or multi-tier data centers. I certainly agree with that mindset. Cloud would not be a multibillion-dollar business today if it wasn’t ready for primetime. 

I’ll start by answering a question that immediately comes to mind: What, exactly, does multi-cloud mean? When we reference a multi-cloud environment, we’re talking about an organization that utilizes some combination of one or more public and/or private clouds to power their critical applications and workloads. For example, an organization may utilize Amazon Web Services (AWS) for its mainstream applications, Google Cloud for machine learning (ML)-centric workloads, and a private on-premises cloud for compliance-governed applications. Sound complicated? It is. 

Most data centers host hundreds—if not thousands—of applications that run business- and mission-critical operations. As organizations consider moving to the cloud, they are faced with questions on how these applications will fit into their cloud strategy and how they can migrate their workloads to a cloud platform with the least risk and disruption to their business.

ConvergeOne recently announced the availability of ConvergeOne Secure Connect, our new software-defined wide area network (SD-WAN) managed services offer. In a nutshell, Secure Connect is a subscription-based, fully-managed SD-WAN that connects our customers’ networks to ConvergeOne Cloud Experience (C1CX) collaboration solutions. I know what you may be thinking: What is SD-WAN? It’s one of those terms that we’ve all heard of before, but few know what it really is, and why it’s a hot topic. Let’s dive a little deeper into SD-WAN and explore why Secure Connect is such a cool offer.