<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by CloudQuickHits on Medium]]></title>
        <description><![CDATA[Stories by CloudQuickHits on Medium]]></description>
        <link>https://medium.com/@CloudQuickHits?source=rss-41751178a515------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pZSnPjMS-2TYjPpv71qptQ.png</url>
            <title>Stories by CloudQuickHits on Medium</title>
            <link>https://medium.com/@CloudQuickHits?source=rss-41751178a515------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:53:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@CloudQuickHits/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Container Sensemaking: What Your Peers Are Up To]]></title>
            <link>https://medium.com/cloud-quick-hits/container-sensemaking-what-your-peers-are-up-to-9add44badf4e?source=rss-41751178a515------2</link>
            <guid isPermaLink="false">https://medium.com/p/9add44badf4e</guid>
            <category><![CDATA[paas]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[iaas]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[containers]]></category>
            <dc:creator><![CDATA[CloudQuickHits]]></dc:creator>
            <pubDate>Tue, 28 Feb 2017 17:19:47 GMT</pubDate>
            <atom:updated>2017-03-10T13:23:24.264Z</atom:updated>
            <content:encoded><![CDATA[<p>You get a container! And, YOU get a container! You get a container! And, You! EVERYBODY GETS A CONTAINER!!!</p><p>Like an Oprah season premiere giveaway, IT organizations across industries are handing out containers to every workload in the room. These containers are filled with hopes and dreams of increasing speed, agility and compression rates. But, is this the wrong approach and the wrong expectation? Not necessarily… but the reality takes away just a bit of the rose-coloring on those glasses. <br> <br>The reality that is shaking out as more and more businesses test container approaches and implementation is that containerization will help some workloads more than others. And if you use them in the wrong way, or for the wrong workload, you’ll end up wasting more time and resources than you save.</p><p>In a recent webinar, Forrester stated they see between 30–35% of businesses testing containerization, with right around 10% running containers in production. That number jumps when you poll DevOps and digitally-transformed businesses, but if we’re cutting across all industries and surveys, the overall market adoption is around 10% today and growing rapidly. Most surveys expect that number to grow to 50% or more in the next 2 years. <br> <br>Those surveys match our one-on-one conversations with clients as well. As more and more businesses shift to defining their core value in the software they deliver to their internal and external customers, stable, innovative deployments become key. Several of our customers that previously defined their core value broadly across multiple services are shifting into software development IT focus as their business transforms and their customers look to consume those services in an application model. <br> <br>Nearly every business we’ve talked to is looking to spend less time on the operational part of their IT business and put that time back into innovation and development efforts, which drives their business forward. Containers, while not the only answer to that problem, are certainly an attractive tool to help shift that work from one bucket to the next. <br> <br>The market is a state of exploration today as they try to figure out what exactly this panacea can truly cure to achieve their business goal. So,<strong> what are your peers learning that you should know?</strong></p><blockquote><strong>Market Understanding #1 —</strong> <strong>Containers are not VMs, and VMs are not Containers.</strong></blockquote><p>Just as cloud-washing was common ten years ago, container-washing can be seen in many places today. The common market understanding is that containers and VMs <em>are</em> fundamentally different in their design, use cases and purpose. <br> <br><a href="https://blog.docker.com/2016/03/containers-are-not-vms/">Docker Technical Evangelist Mike Coleman</a> describes the difference this way, “With containers, you share the underlying resources of the Docker host and you build an image that is exactly what you need to run your application. You start with the basics and you add what you need. VMs are built in the opposite direction. You are going to start with a full operating system and, depending on your application, might be strip out the things you don’t want.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*iO1NM20ArzjmeFVi36UeJw.jpeg" /></figure><p><em>Image from SDXcentral.com: </em><a href="https://www.sdxcentral.com/cloud/containers/definitions/containers-vs-vms/"><em>https://www.sdxcentral.com/cloud/containers/definitions/containers-vs-vms/</em></a></p><blockquote>Market Understanding #2 — <strong>Containers and VMs are not mortal enemies.</strong></blockquote><p>Containers and VMs are not oil and water. They mix well together, and in fact, we expect most future datacenters will have both, each with its ideal use case and workload fit. In today’s world however, many companies are taking to learning containers within their existing environments — which means deploying containers within a VM. <br> <br> As containers continue to mature, many analysts and experts are recommending this in-VM deployment model to increase stability and security of the containers. While it’s assumed this is not necessarily the ideal long-term model, it’s an generally agreed upon ideal starter approach for many businesses who have VM expertise in-house already, or have established IaaS hosting partnerships, because the approach allows your team to learn the tool without learning new operational overhead of shifting to a bare metal provider. <br> <br> Containers require a new way of thinking, servicing and approaching application deployment and development, so deploying containers in VMs to start can be a nice set of training wheels to gain value without introducing too much risk.</p><blockquote>Market Understanding #3 — <strong>There’s no one right place to run containers.</strong></blockquote><p>Some think containers are equal to cloud, but that’s just not the case. Containers can run in hyper-scale clouds, in managed cloud hosting providers, in private clouds and on bare metal. There’s nothing about containers that require hosting in a certain type of environment over the other. <br> <br> Rather than have the architecture of the application dictate the location of its hosting, the location should be dictated by the business needs of the application. This is one area that doesn’t fundamentally change from the past. If your application’s business needs put it as a best-fit in the cloud, it can stay in cloud in its new architecture model. If it was a best fit on-prem previously, that doesn’t have to change simply due to the architecture model in the future.</p><blockquote>Market Understanding #4 — <strong>“Mode 2”, or cloud-native apps are a better fit than your incumbent/legacy “Mode 1” apps</strong></blockquote><p>In an ideal future world, every application would leverage the latest and greatest technology. But, reality states that’s likely never going to happen. Just as many companies never achieved 100% virtualization, the reality of resource constraints says most companies will not be able to re-architect all of their applications; it’s just not feasible.</p><p>In the near-term, “Mode 2” and cloud-native apps are going to be the best fit to adopt containers, often in concert with microservices. By the nature of where they are today, it’s going to be easier to take advantage of the benefits of containerization and DevOps practices with these applications. Re-architecting “Mode 1” applications requires time, money and overhead that often can’t be spared when weighed against everything else on the team’s priority list.</p><p>Transformation doesn’t happen in a day, and this is going to be a lengthy learning process for everyone in the market. As the technology evolves, we’re going to learn more and gain efficiencies in the process. What should be comforting to know, however, is the key to success with containers doesn’t change from the past. <strong>Take small steps, keep learning, ask questions and share what you’ve learned, when you can.</strong></p><p><em>— Diana Nolting is a Product Analyst at Bluelock, an industry-leading Disaster Recovery-as-a-Service provider for complex environments and sensitive data.</em> <em>With five years experience in the cloud service provider market, Nolting pairs her insatiable appetite for consuming information with user interviews, industry articles and analyst reports. She transitioned to the tech world from the media and sports entertainment industry and holds a Bachelors of Journalism from Indiana University Bloomington. Connect with Diana on twitter at </em><a href="http://www.twitter.com/diananolting"><em>@diananolting</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9add44badf4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloud-quick-hits/container-sensemaking-what-your-peers-are-up-to-9add44badf4e">Container Sensemaking: What Your Peers Are Up To</a> was originally published in <a href="https://medium.com/cloud-quick-hits">Cloud Quick Hits</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pushing Bits: Everything Under the Rug of Data Replication]]></title>
            <link>https://medium.com/cloud-quick-hits/pushing-bits-the-iceberg-underneath-successful-data-replication-331bf03aab88?source=rss-41751178a515------2</link>
            <guid isPermaLink="false">https://medium.com/p/331bf03aab88</guid>
            <category><![CDATA[disaster-recovery]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[network]]></category>
            <category><![CDATA[replication]]></category>
            <category><![CDATA[data-replication]]></category>
            <dc:creator><![CDATA[CloudQuickHits]]></dc:creator>
            <pubDate>Tue, 28 Feb 2017 12:18:48 GMT</pubDate>
            <atom:updated>2017-03-10T13:24:52.004Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the most challenging technical bits when designing a disaster recovery plan is moving the data. Unfortunately, it is too easy (both mentally and verbally) to brush over the myriad of complexities with just one word… “replication”.</p><p>Don’t get me wrong, there are a lot of important facets to getting DR right, from strategy to playbooks, but if you are going to have a useful and reliable recovery, your <strong>data moving strategy</strong> needs to be sound.</p><p>Don’t hit your boat on the weight of the iceberg under the surface, consider these five areas as part of your replication strategy.</p><p><strong>Network Topology</strong> — While it seems obvious that you need to know where plumbing goes, one nuances that is often overlooked is the distinction between the replication channel and the control channel.</p><ul><li>The control channel often does not need much bandwidth, but it does need administrative access to you SAN controller or replication software, which often requires OS or hypervisor admin privileges. This highly privileged access crosses departmental and functional boundaries, so <strong>care should be taken to ensure that access to these control networks is very secure and that role-based access control is setup with only the permissions needed to manage the replication</strong>.</li><li>The replication channel is where the heavy work is done. All the bits are going to flow over this channel and <strong>it is critical that the replication channel is as simple and robust as can be</strong>. In many cases the control channel can be interrupted without impacting the data replication, but if the replication channel is broken, it can cause resending or even re-checksum of large sections of data. The replication channel will be carrying large, encrypted data blocks which are easy to route, but expensive to inspect and virtually impossible to compress. <strong>Consider deploying technology that performs security and optimization measures before the data is transmitted</strong> to get the most out of your bandwidth, routing and switching technology. Also, be careful that the network components on this channel can handle the full bandwidth and packet sizes of your replicated data.</li></ul><p><strong>Security </strong>— The fact that data is being lifted and sent out of the datacenter is probably the reason the entire security budget exists. To ensure that it stays safe during this process, take a close look at your security policy that applies to the data being replicated and <strong>ensure that the way it is being transmitted, landed, and handled is in line with your internal policy</strong>. Many security concerns can be handled with a combination of VPN encryption and by ensuring that it lands on a target with encrypted storage.</p><p><strong>Rate of Change</strong> — How much data are you going to be moving? This is a multifaceted variable based on rate of change, data compression, encryption, and caching to name a few factors. One way to get a rough estimate of the amount of data you will be moving is to <strong>take a look at the size of the nightly backups for the workloads you are protecting.</strong> This won’t capture data that changes state multiple times in a day, but it will get you started.</p><p><strong>Bandwidth </strong>— Once you know roughly how much data you’ll be moving, calculating the amount of bandwidth needed is a math problem.<strong> A rough rule of thumb is that it takes</strong> <strong>roughly 1 Megabit to move 10GB in 24 hours</strong>. So, if you have 1TB daily change, you’d need to start thinking about over a 100Mb pipe. But, you don’t want to make the pipe that tight. You need to be able to handle resync and change spikes and you can only really only count on 60%-70% of that pipe as usable. TCP and VPN overhead can eat up the rest depending on replication tools and packet size. You get better pipe utilization if your replication is tuned to send fewer, larger packets instead of lots of smaller ones.</p><p><strong>Transaction Consistency</strong> — Transaction consistency isn’t just about making sure the database comes up clean. If your App server has queued transactions that the DB server has already processed, it could end up running them again if the two servers are not in sync. <strong>Make sure to choose replication technology that understands how to keep multiple servers replicating in lock-step</strong>.</p><p>While designing your Disaster Recovery plans, it’s easy to sweep a lot of details under the rug of the word “replication”. Don’t underestimate the impact the topology, security, rate of change, bandwidth and transaction consistency needs can have on the initial and ongoing success of your strategy, and plan to take time for a deeper look into these details.</p><p><em>— Ben Miller is Product Solution Director at Bluelock, an industry-leading Disaster Recovery-as-a-Service provider for complex environments and sensitive data.</em> <em>An expert in cloud computing solutions with a background in technical consulting, managed IT services, and disaster recovery, Miller has more than 20 years of experience in solving cloud, virtualization and enterprise system IT problems across industries. Miller holds an MS in Instructional Systems Technology from Indiana University Bloomington. Connect with Ben on twitter at </em><a href="http://www.twitter.com/vmFoo"><em>@vmFoo</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=331bf03aab88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloud-quick-hits/pushing-bits-the-iceberg-underneath-successful-data-replication-331bf03aab88">Pushing Bits: Everything Under the Rug of Data Replication</a> was originally published in <a href="https://medium.com/cloud-quick-hits">Cloud Quick Hits</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>