Cloud computing is no longer just a buzzword, it is here to stay. Companies should prepare by looking into cloud technology and getting their cloud strategy sorted out. If you look at cloud computing in its most basic form, you could simply call it store stuff on the internet. Although this is partially true, the cloud has much more to offer.
Preparing for the cloud means a fundamental change of perspective on computer technology, especially on how we use computing power. The cloud’s main advantage is that it has the ability to turn software into a service. Customers only pay for what they actually need, turning computing power and storage space into a parameter that you can buy when you need it, and be scaled up when necessary.
What most people miss out on is the cloud’s ability to shift your IT expense from CAPEX to OPEX. Evenly important and often overlooked is how the price of a 1U server is compared to an Azure server. Usually the average selling price is divided by the number of months of the server’s typical expected service life (36 or 48 months), showing that the total cost per month is lower than the same server from Azure. People tend to conclude that cloud computing is bound to be more expensive than self-owned and therefore the cloud is considered inappropriate for typical corporate apps that require round-the-clock availability. This line of thought, however, completely overlooks the fact that the real cost of hosting a server consists of immediately paying for the foreseen overhead in three to four years. You risk throwing away even more money if you make a mistake in either direction during the sizing phase.
Assume the sizing is done correctly and the estimates predict that you will need a €25,000 server with 8 cores and 48 GB ram, costing you €100,000 on licenses. Because of the predictable growth of the application this means that:
So your TCO for 4 years is (excluding interest, various overhead factors, maintenance and electricity) €125,000 or bluntly put €2,605/month. The same server in Azure cists €2,736/month. The quick and dirty conclusion is that cloud is ± 5% more expensive, which to critics is the proof they need that internal servers are cheaper. Unfortunately, this conclusion is a losing strategy because it fails to incorporate the cloud’s greatest power: flexibility.
This brings your TCO to €93,168 instead of €125,000, which is 25% cheaper than previous calculations, simply by using the cloud in its simplest form. Even greater profits are possible by changing the way we think about IT assets.
The cloud may be more economical, but this doesn’t mean that you should switch just like that. Moving to the cloud requires a certain level of self-examination, because one size won’t fit all.
Some important examples are:
In short, you’ll need to map your company’s and business units’ IT needs to decide on the right cloud strategy. For example, if you’re hosting your own applications, the source code might be really sensitive. For others, such as servicing hospitals, the data itself is really sensitive. This is why you shouldn’t just ask yourself what you should put in the cloud, but also how and where.
The cloud should never be seen as a goal on itself. It is a tool, enabling you to achieve your goals, targets or SLA’s. Going to the cloud often means that you’ll need to release some flexibility and control, but you will get scalability and power in return. If you look at the cloud in that way, the questions you should ask yourself are easier to answer.
When going to the cloud always make sure you are able to describe how data or assets will need to be secured. After creating this security mapping, start to investigate how you can achieve this. Divided security into two solid blocks; one being access security ─ encryption/passwords/access control/auditing─, and the other one being the storage and protection of data itself ─ backups/retention/storage location/storage type).
Try to avoid thinking in terms of servers and start thinking in term of individual services. You don’t actually need a full database server running in the cloud when you can do with just a database, or even smaller, a table. By allowing this kind of granularity, you will be able to harness the true power of the cloud. A database server only becomes needed if you need several databases, facilitating the business decision when to use what kind of service you actually need (for example IAAS vs. PAAS).
The easiest way to learn about how the cloud performs, is to start using it in Dev and/or test it. This allows you to start your cloud adventure without having to worry about confidential data or mission-critical systems, building confidence and experience. If the service works, you can expand with peace of heart and confidence. After all, this is what Gartner experts advise to their customers: first put a small [cloud service] in place and see what unexpected behaviors happen.
Cookie | Duration | Description |
---|---|---|
ARRAffinity | session | ARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user. |
ARRAffinitySameSite | session | This cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |
pll_language | 1 year | Polylang sets this cookie to remember the language the user selects when returning to the website and get the language information when unavailable in another way. |
Cookie | Duration | Description |
---|---|---|
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gat_gtag_UA_* | 1 minute | Google Analytics sets this cookie to store a unique user ID. |
_gid | 1 day | Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously. |
ai_session | 30 minutes | This is a unique anonymous session identifier cookie set by Microsoft Application Insights software to gather statistical usage and telemetry data for apps built on the Azure cloud platform. |
CONSENT | 2 years | YouTube sets this cookie via embedded YouTube videos and registers anonymous statistical data. |
vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
Cookie | Duration | Description |
---|---|---|
ai_user | 1 year | Microsoft Azure sets this cookie as a unique user identifier cookie, enabling counting of the number of users accessing the application over time. |
VISITOR_INFO1_LIVE | 5 months 27 days | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt.innertube::nextId | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
WFESessionId | session | No description available. |