What's Behind The Cloud

Post: Whats Behind the Cloud, and Why is it Important?

What’s Behind the Cloud, and Why is that Important?

Cloud Computing has been one of the most profoundly evolutionary advances for tech spaces around the world. Among other things, it allows firms to reach new levels of productivity, efficiency and has birthed new revolutionary business models.


That being said, it seems as though there remains some confusion about what this technology is, and what it really means. We hope to clear some of that up today.

What is the Cloud, simply?

Typically, Cloud Computing is defined as online, over the internet “resources.” These “resources” are an abstraction of things like storage, computational power, infrastructure, platforms, and more. Critically, and most beneficially to users of the Cloud, all of these resources are managed by somebody else.


Cloud computing is everywhere and underlies a lot of software. Here are three big examples of the Cloud in the wild, along with a brief description of how the technology comes into play and affects the business.


The video conference software that took the world by storm in 2020 is an example of a Cloud-based program. People don’t tend to think of Zoom in that way, but that doesn’t change the fact of the matter. It exists as a central server that receives your video and audio data, and then forwards that to everybody on the call.

Zoom is unlike similar peer-to-peer video conferencing software wherein a direct connection is made between two users. This key difference is what makes the program so uniquely lightweight and flexible.

Amazon Web Services

AWS is more central to the category of Cloud-based services and is one of the most well-known examples of the technology in action. Essentially, it turns server space into a service, providing more or less infinite room to be “rented” by different firms.

With AWS, you’re able to dynamically expand and contract capacity in accordance with demand, something impractical (if not impossible) without a third party managing the actual physical infrastructure separately from your own company. If you run servers in-house, then you need to own and maintain all of the hardware (and staff) to keep up with peak usage all the time.


This file-sharing service, similar to AWS, is very famously a Cloud-based solution to the problem of storage. In short, it allows users to connect to a central “hard drive,” the physical nature of which is utterly unknown to the users.

Outside of a Cloud context, acquiring and maintaining storage entails investigating the right hardware, purchasing the physical drives, installing them, and maintaining them – not to mention the downtime during and between these stages. With Dropbox, all of this goes away. The entire process is highly abstracted and consists of buying “storage space” digitally, and putting things in it.

Private vs Public Clouds

All the examples of Cloud computing we’ve talked about so far have been in a public context; however, the technology is more broadly applicable than just these cases. The same central foundational benefits that the Cloud provides users can be condensed and localized into a local version, not accessed or provided over the internet.

The Private Cloud

While ostensibly an oxymoron, Private Clouds operate on fundamentally the same principles as Public ones – some service (servers, storage, software) is managed separately from the main body of the company. Critically, this separate group dedicates its services solely to its parent company, providing all the benefits without many of the security drawbacks.

To explain it with a metaphor, let’s imagine that clouds are like lockers. You can rent space in a public locker and store your stuff in a convenient location without making too many compromises. For some people, this solution is untenable. One option they could exercise is to rent out the entire building – every locker is dedicated entirely to themselves. These lockers would still be managed by a separate company, but aren’t shared with just any client.

For some organizations of a large enough size dealing with sensitive enough information, this solution doesn’t just make practical sense, it’s absolutely necessary.

What does the Cloud mean?

There are numerous benefits to Cloud computing, both in its private and public forms. These all stem from the central fact that managing a Cloud-based piece of software is more hands-off for the client. For a more detailed analysis, consider these three primary benefits.


Because you have a small team of specialists managing just one project, they’re able to (in theory) get it working to a very high level of competence. It’s similar to free market concepts wherein certain economies focus their energy on producing what they’re naturally optimized for, and then trade the surplus for what they lack – a non-zero-sum game where everybody benefits from everybody specializing.


In a similar vein, a firm is much better able to respond to supply and demand if it can dynamically expand and contract parts of its business at will. Unpredictable shifts in the market are much less devastating or can be much better exploited with faster reflexes.


The remote aspect of Cloud computing has not been focused on too heavily in this article but is still nonetheless extremely important and valuable. To return to the Dropbox example, allowing anybody to access the same files anywhere from basically every platform as long as it has an internet connection is incredibly powerful and valuable for any firm.

So Which Do You Choose?

In conclusion, whether a private or public Cloud, this revolutionary advancement in the way technology is developed and distributed has many far-reaching applications and incredible benefits. These include making firms more efficient, more flexible, and more responsive.


We’ve found that all too often, companies still tend to think a little too inside the box about what the Cloud is truly capable of. This can range from not thinking in terms of private Cloud solutions, to not considering anything past an AWS-type situation.

The horizon is broad and the Cloud has only begun to reign in tech spaces.


Scroll to Top
As the BI space evolves, organizations must take into account the bottom line of amassing analytics assets.
The more assets you have, the greater the cost to your business. There are the hard costs of keeping redundant assets, i.e., cloud or server capacity. Accumulating multiple versions of the same visualization not only takes up space, but BI vendors are moving to capacity pricing. Companies now pay more if you have more dashboards, apps, and reports. Earlier, we spoke about dependencies. Keeping redundant assets increases the number of dependencies and therefore the complexity. This comes with a price tag.
The implications of asset failures differ, and the business’s repercussions can be minimal or drastic.
Different industries have distinct regulatory requirements to meet. The impact may be minimal if a report for an end-of-year close has a mislabeled column that the sales or marketing department uses, On the other hand, if a healthcare or financial report does not meet the needs of a HIPPA or SOX compliance report, the company and its C-level suite may face severe penalties and reputational damage. Another example is a report that is shared externally. During an update of the report specs, the low-level security was incorrectly applied, which caused people to have access to personal information.
The complexity of assets influences their likelihood of encountering issues.
The last thing a business wants is for a report or app to fail at a crucial moment. If you know the report is complex and has a lot of dependencies, then the probability of failure caused by IT changes is high. That means a change request should be taken into account. Dependency graphs become important. If it is a straightforward sales report that tells notes by salesperson by account, any changes made do not have the same impact on the report, even if it fails. BI operations should treat these reports differently during change.
Not all reports and dashboards fail the same; some reports may lag, definitions might change, or data accuracy and relevance could wane. Understanding these variations aids in better risk anticipation.

Marketing uses several reports for its campaigns – standard analytic assets often delivered through marketing tools. Finance has very complex reports converted from Excel to BI tools while incorporating different consolidation rules. The marketing reports have a different failure mode than the financial reports. They, therefore, need to be managed differently.

It’s time for the company’s monthly business review. The marketing department proceeds to report on leads acquired per salesperson. Unfortunately, half the team has left the organization, and the data fails to load accurately. While this is an inconvenience for the marketing group, it isn’t detrimental to the business. However, a failure in financial reporting for a human resource consulting firm with 1000s contractors that contains critical and complex calculations about sickness, fees, hours, etc, has major implications and needs to be managed differently.

Acknowledging that assets transition through distinct phases allows for effective management decisions at each stage. As new visualizations are released, the information leads to broad use and adoption.
Think back to the start of the pandemic. COVID dashboards were quickly put together and released to the business, showing pertinent information: how the virus spreads, demographics affected the business and risks, etc. At the time, it was relevant and served its purpose. As we moved past the pandemic, COVID-specific information became obsolete, and reporting is integrated into regular HR reporting.
Reports and dashboards are crafted to deliver valuable insights for stakeholders. Over time, though, the worth of assets changes.
When a company opens its first store in a certain area, there are many elements it needs to understand – other stores in the area, traffic patterns, pricing of products, what products to sell, etc. Once the store is operational for some time, specifics are not as important, and it can adopt the standard reporting. The tailor-made analytic assets become irrelevant and no longer add value to the store manager.