{"id":264764,"date":"2021-06-02T15:00:39","date_gmt":"2021-06-02T12:00:39","guid":{"rendered":"https:\/\/en.buradabiliyorum.com\/5-cloud-architecture-mistakes-we-shouldnt-still-be-making-cloudsavvy-it\/"},"modified":"2021-06-02T15:00:39","modified_gmt":"2021-06-02T12:00:39","slug":"5-cloud-architecture-mistakes-we-shouldnt-still-be-making-cloudsavvy-it","status":"publish","type":"post","link":"https:\/\/buradabiliyorum.com\/en\/5-cloud-architecture-mistakes-we-shouldnt-still-be-making-cloudsavvy-it\/","title":{"rendered":"#5 Cloud Architecture Mistakes We Shouldn\u2019t Still Be Making \u2013 CloudSavvy IT"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_84 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-6a2b0799aed31\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #dd3333;color:#dd3333\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #dd3333;color:#dd3333\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-6a2b0799aed31\" checked aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/buradabiliyorum.com\/en\/5-cloud-architecture-mistakes-we-shouldnt-still-be-making-cloudsavvy-it\/#1_Blind_Focus\" >1. Blind Focus<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/buradabiliyorum.com\/en\/5-cloud-architecture-mistakes-we-shouldnt-still-be-making-cloudsavvy-it\/#2_Provisioning_Errors\" >2. Provisioning Errors<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/buradabiliyorum.com\/en\/5-cloud-architecture-mistakes-we-shouldnt-still-be-making-cloudsavvy-it\/#3_No_Room_for_Change\" >3. No Room for Change<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/buradabiliyorum.com\/en\/5-cloud-architecture-mistakes-we-shouldnt-still-be-making-cloudsavvy-it\/#4_No_Migration_Plan\" >4. No Migration Plan<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/buradabiliyorum.com\/en\/5-cloud-architecture-mistakes-we-shouldnt-still-be-making-cloudsavvy-it\/#5_Deprioritizing_Security\" >5. Deprioritizing Security<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/buradabiliyorum.com\/en\/5-cloud-architecture-mistakes-we-shouldnt-still-be-making-cloudsavvy-it\/#Summary\" >Summary<\/a><\/li><\/ul><\/nav><\/div>\n<p><strong>&#8220;#5 Cloud Architecture Mistakes We Shouldn\u2019t Still Be Making \u2013 CloudSavvy IT&#8221;<\/strong><\/p>\n<div id=\"article-content-area\">\n<figure style=\"width: 2832px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" class=\"type:primaryImage wp-image-11684 size-full\" data-pagespeed-lazy-src=\"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2021\/06\/040efef6.png?width=1198&amp;trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"Room full of servers\" width=\"2832\" height=\"1388\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><figcaption class=\"wp-caption-text\"><span class=\"type:primaryImage imagecredit\"><a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.shutterstock.com\/image-illustration\/network-server-room-computers-digital-communications-715802656\">Shutterstock\/Connect world<\/a><\/span><\/figcaption><\/figure>\n<p>Adoption of cloud computing has grown rapidly over the past few years. Many organizations are now dependent on their cloud systems. This leaves less room for error when designing new architectures.<\/p>\n<p>A poorly planned system can be a burden on the business that\u2019s using it. Reconfiguring an architecture is a costly and time-consuming process, especially if the original cloud migration didn\u2019t go smoothly. While some mistakes are unavoidable, here\u2019s five gotchas that you should watch out for.<\/p>\n<h2 id=\"blind-focus\"><span class=\"ez-toc-section\" id=\"1_Blind_Focus\"><\/span>1. Blind Focus<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Cloud technologies are still surrounded by a degree of hype and buzz. This can prompt organizations to fixate on the latest \u201cbig thing,\u201d even if an older solution might actually be more <a href=\"https:\/\/buradabiliyorum.com\/en\/category\/download-scripts-themes-apps\/\" data-internallinksmanager029f6b8e52c=\"9\" title=\"Download Scripts &amp; Themes &amp; Apps\" target=\"_blank\" rel=\"noopener\">app<\/a>ropriate.<\/p>\n<p>Don\u2019t move to the cloud just because you can. Evaluate your options objectively within the context of your operations. Assuming that the cloud will solve all of your IT infrastructure issues is one of the biggest mistakes that you can make. A successful migration requires you to adopt a cloud-first mindset, not a list of technologies and service providers.<\/p>\n<p>A poorly considered cloud migration could compound any existing organizational problems. Widely distributing services across different platforms impedes your ability to oversee your systems. You\u2019ll need to learn new management tools and processes so that you can retain control.<\/p>\n<p>Adopting cloud <a href=\"https:\/\/buradabiliyorum.com\/en\/category\/technology\/\" data-internallinksmanager029f6b8e52c=\"4\" title=\"Technology\" target=\"_blank\" rel=\"noopener\">technology<\/a> has a cost attached. This is normally borne out within the time frame necessary to retrain staff as they adapt to the new system. You should assess each workload to determine whether it makes sense to move it to the cloud. Not every migration will be worth it.<\/p>\n<p>Don\u2019t lose sight of where your data is stored. You need to know where your servers are located, how many servers you have, and how data is being distributed across them. Remember, you\u2019re not moving to an all-encompassing cloud that you can set and forget. It\u2019s important to document how your architecture functions and where your data resides.<\/p>\n<p>Cloud migrations should be driven by a legitimate business need. You need to be able to identify what a cloud system will add to your organization. Otherwise, you can end up with costly infrastructure that\u2019s underutilized and poorly aligned with your operations.<\/p>\n<h2 id=\"provisioning-errors\"><span class=\"ez-toc-section\" id=\"2_Provisioning_Errors\"><\/span>2. Provisioning Errors<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The cloud makes it simple to spin up new instances of servers, services, and data stores. Unfortunately, this can result in unoptimized provisioning, which swallows your budget and can impact performance.<\/p>\n<p>Shared servers might make sense for some components of your stack. If you have 10 servers that sit idle for most of the day, it might make more sense to consolidate onto a single machine.<\/p>\n<p>Remember that \u201cthe cloud\u201d still carries the basic rules of hardware architecture design. Although you can create dozens of servers spread across geographical regions, doing so can increase latency and requires sustainable levels of network throughput.<\/p>\n<p>These problems are particularly prevalent in larger organizations, where individual departments are permitted to create their own infrastructure. You can quickly end up with an instance count that far exceeds your cost estimates.<\/p>\n<p>If an individual leaves the organization, infrequently used instances might be forgotten. Keep an inventory of your cloud servers so that you know when instances have become redundant. In small teams, it can be more sustainable to let co-workers spin up virtual machines on a shared server. Providing full access to a cloud environment could quickly prove regrettable.<\/p>\n<h2 id=\"no-room-for-change\"><span class=\"ez-toc-section\" id=\"3_No_Room_for_Change\"><\/span>3. No Room for Change<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Cloud is the technology of today. If there\u2019s one thing that\u2019s evident from past decades, it might not necessarily be relevant tomorrow. Although the <a href=\"https:\/\/buradabiliyorum.com\/en\/category\/general\/\" data-internallinksmanager029f6b8e52c=\"3\" title=\"General\" target=\"_blank\" rel=\"noopener\">general<\/a> notion of \u201cputting it in the cloud\u201d seems unlikely to disappear, individual technologies evolve and get replaced on a regular basis.<\/p>\n<p>If you\u2019re taking the time to migrate to the cloud, do yourself a favor and use the opportunity to assess how your systems can accommodate change. This exercise is also helpful in determining an effective migration strategy.<\/p>\n<p>Designing for change often involves splitting up monoliths into individual microservices. That in itself might require substantial refactoring, but it can pay dividends in the long term.<\/p>\n<p>Once you\u2019ve adopted a microservices architecture, you have the freedom to locate each individual service in the cloud that fits it best. If a technology gets superseded in the future, you\u2019ll be able to focus on migrating the specific microservices that utilized it.<\/p>\n<p>On a grander scale, cloud providers might evolve their product stacks, merge together, or shut down. You should make plans for how your system will respond to these events, however unlikely they might seem. Don\u2019t assume that the situation today will remain the same forever.<\/p>\n<h2 id=\"no-migration-plan\"><span class=\"ez-toc-section\" id=\"4_No_Migration_Plan\"><\/span>4. No Migration Plan<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Implementing a cloud architecture isn\u2019t something that you do in an afternoon. Successful migrations require an action plan that fully considers all contingencies. You should make sure that all stakeholders are informed about what\u2019s going on, why it\u2019s needed, and how you\u2019ll respond to any unforeseen issues.<\/p>\n<p>You should aim to gradually migrate your workloads. If you move everything in one go, any problem will be much more impactful. Starting with a relatively low-traffic service will give you more breathing room if something goes wrong.<\/p>\n<p>Evaluate each migration to identify learnings that you can apply to the next one. Gradually ramp up your cloud adoption until you\u2019re where you want to be. A migration could end up being a multi-month exercise, but this gives you more time to analyze its effects on your organization.<\/p>\n<p>If nothing else, a documented strategy is important so that you have a reference for the future. Your successors will thank you if you can point them to a migration plan that explains how your infrastructure reached its current state. It\u2019s important to detail the business case for each stage as well as the technical details. This helps illustrate <em>why<\/em> a system was chosen instead of merely describing <em>what<\/em> was installed.<\/p>\n<h2 id=\"deprioritising-security\"><span class=\"ez-toc-section\" id=\"5_Deprioritizing_Security\"><\/span>5. Deprioritizing Security<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This list wouldn\u2019t be complete without mentioning security. Security needs to be more than an afterthought. It should be baked into every aspect of your architecture. Shifting security to the start of your decision-making process ensures that it can\u2019t be overlooked.<\/p>\n<p><strong>RELATED:<\/strong> <strong><em>What Are the Three Pillars of Cybersecurity?<\/em><\/strong><\/p>\n<p>Don\u2019t assume that your cloud systems are inherently secure. Use of big-name providers can provide false reassurance that your data is protected. In reality, no cloud is completely secure. Many serious breaches originate from basic configuration mistakes, such as unintentionally exposing an object storage bucket.<\/p>\n<p>Integrating security into your design reduces the risk of hidden issues. Having a single audit at the end of your process might cause you to miss vulnerabilities that lie within individual components.<\/p>\n<p>Systemic security integration adds time and cost to the initial build but is vital for long-term use. You need to consider every eventuality in which an attacker could gain access to your servers, data, and configuration stores.<\/p>\n<p>Remember to lock down access to cloud host control panels, too. It\u2019s no good having stringent workload security protections if you\u2019re using an unsecured password to access your hosting provider. Use a strong password, set up two-factor authentication, and only delegate access to essential team members.<\/p>\n<h2 id=\"summary\"><span class=\"ez-toc-section\" id=\"Summary\"><\/span>Summary<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>An effective cloud architecture helps you maximize the opportunities provided by your systems. Cloud technology can be more efficient, more scalable, and easier to integrate with other services. That doesn\u2019t mean that it\u2019s your only option, though.<\/p>\n<p>Assess the full spectrum of available technologies, create a detailed plan before you migrate, and be open to change. Integrate security from the start so that you know your data is safe. You might still make mistakes, but at least you\u2019ll be better prepared to anticipate and resolve them.\n<\/p><\/div>\n<blockquote><p><strong><span style=\"color: #ff6600;\">If you liked the article, do not forget to share it with your friends. Follow us on\u00a0<span style=\"color: #ff0000;\"><a style=\"color: #ff0000;\" href=\"https:\/\/news.google.com\/publications\/CAAqBwgKMLG0nwswvr63Aw\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Google News<\/a><\/span>\u00a0too, click on the star and choose us from your favorites.<\/span><\/strong><\/p><\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\">For forums sites go to <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/forum.buradabiliyorum.com\/\" target=\"_blank\" rel=\"noopener\">Forum.BuradaBiliyorum.Com<\/a><\/span><\/strong><\/p>\n<\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\"><strong>If you want to read more like this article, you can visit our <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/en.buradabiliyorum.com\/technology\/\" target=\"_blank\" rel=\"noopener\">Technology category.<\/a><\/span><\/strong><\/p>\n<\/blockquote>\n<p><span style=\"color: black;\"><a style=\"color: #ff9900;\" href=\"https:\/\/www.cloudsavvyit.com\/11445\/5-cloud-architecture-mistakes-we-shouldnt-still-be-making\/\" target=\"_blank\" rel=\"noopener\">Source<\/a><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;#5 Cloud Architecture Mistakes We Shouldn\u2019t Still Be Making \u2013 CloudSavvy IT&#8221; Shutterstock\/Connect world Adoption of cloud computing has grown rapidly over the past few years. Many organizations are now dependent on their cloud systems. This leaves less room for error when designing new architectures. A poorly planned system can be a burden on the&#8230;<\/p>\n","protected":false},"author":1,"featured_media":264765,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2021\/06\/040efef6.png","fifu_image_alt":"","footnotes":""},"categories":[18],"tags":[],"class_list":["post-264764","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/264764","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/comments?post=264764"}],"version-history":[{"count":0,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/264764\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media\/264765"}],"wp:attachment":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media?parent=264764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/categories?post=264764"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/tags?post=264764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}