The Cloud: How QDivision Utilizes Cloud Infrastructure to Optimize Performance

What is “The Cloud” and how does QDivision utilize it? Great question! Read on to learn about cloud infrastructure and what the team at QDivision is accomplishing to support our overall business goals.

Is “The Cloud” just someone else’s computer?

It’s a common meme and an easy joke to make that “The Cloud” is just someone else’s computer, but it would not be true.

Cloud Deployments vary from very simple to very complex. 

It all depends on a what the requirements are.  A simple hosted static website is a cloud deployment.  On the other hand, a distributed application with hundreds of computer instances, running applications, databases, and various messaging subsystems supporting many thousands of users also counts as a cloud deployment.

What is Cloud Infrastructure?

Cloud Infrastructure is all the pieces needed to support a given cloud infrastructure.  You can configure:

QDivision Cloud Infrastructure

The Cloud Infrastructure Team at QDivision

Here at Q Division the Cloud Infrastructure team is the gateway to Cloud resources.

The cloud infrastructure team’s primary focus is to support QDivision’s Application Development efforts and provide access to cloud services.

We utilize cloud providers managed services like AWS or Google Cloud  where possible to maximize team effectiveness.  Utilization of managed services frees the Cloud Infrastructure Team to pursue other efforts rather than having to focus on maintaining additional software platforms.

We also focus on task automation and infrastructure as code to make repeatable standard tasks.  Depending on the task there are a number of tools available such as Ansible and Terraform.

Part of that focus is maintaining and utilizing OKD  as a PaaS to deploy containerized applications/services.  The Cloud Infrastructure Team supports and maintain the Development Pipeline utilizing OKD and Jenkins empower development teams to provision their own pipelines and manage their own Deployments (thru to Production).

How is this different?

In the “old days,” when development teams started on a new project, they need to submit requests for servers for compute resources for new applications, requests DNS names for even in-house network names, requests for load balancer configurations.  These requests could take weeks to complete due to lack of automation, and additional requests by the server teams to other backend teams for resources.

These days Development Teams are able to provision Pipeline Projects for new applications in OKD automatically.  In house network hostnames in development domains are available instantly.  While there are still services which require requests, many of those requests are routine and often fulfilled same day due to Infrastructure as Code calling Cloud Managed Services rather than needing to Provision Servers, Install/Configure Software, configure backups, etc.

For requests for Cloud Services new to QDivision, the Cloud Infrastructure team partners with Development Teams to clarify requirements and work thru details of various solutions to determine the best fit and cost analysis.

The effect is the Cloud Infrastructure team is a force multiplier for our Development Teams so they can focus on writing and deploying great software rather than having to worry about planning out the infrastructure.

The Cloud is not just someone else’s computer.

It is complex with new Technology and aaS offerings being released at an astounding rate.  It is the future of IT and it is our current direction here at QDivision.

Chad Ernst, Tech Lead, Cloud Infrastructure Team, QDivision

To read more interesting information from QDivision, go here.

Supporting sources to read up on as suggested by Chad:

Leave a Comment

Contact Us

We're not around right now. But you can send us an email and we'll get back to you, asap.

Not readable? Change text. captcha txt