<?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 Tushar Agarwal on Medium]]></title>
        <description><![CDATA[Stories by Tushar Agarwal on Medium]]></description>
        <link>https://medium.com/@tushar.agarwal?source=rss-7ad6274d3c00------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oDKoVwNd_TSjCfKMUeqKfw.jpeg</url>
            <title>Stories by Tushar Agarwal on Medium</title>
            <link>https://medium.com/@tushar.agarwal?source=rss-7ad6274d3c00------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:43:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tushar.agarwal/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[Register for our upcoming webinar on AWS Greengrass!]]></title>
            <link>https://medium.com/globallogic-cloud-and-devops-blogs/register-for-our-upcoming-webinar-on-aws-greengrass-a2f43f1f2edc?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2f43f1f2edc</guid>
            <category><![CDATA[aws-greengrass]]></category>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Fri, 28 Jun 2019 07:42:04 GMT</pubDate>
            <atom:updated>2019-06-28T07:42:04.425Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*8ygIrnQ7JuTqTOf4zO61tg.png" /></figure><p>We are inviting you to participate in the first ever public AWS partner webinar on “<strong>Overview of new features in AWS Greengrass</strong>” on Thu, Jul 11, 2019.</p><h3><strong>Overview</strong></h3><p>AWS Greengrass is a toolkit for Edge Computing provided by Amazon Web Services. This software lets you run local computing, messaging, data caching, sync, and ML inference capabilities on connected devices in a secure way. With AWS Greengrass, connected devices can run AWS Lambda functions, keep device data in sync, and communicate with other devices securely.</p><p>Recently Amazon has released some new features that dramatically facilitate the development and deployment, such as:</p><ul><li>Containerized deployment using Docker: now there is no need in special hardware or EC2 instances to run Greengrass core</li><li>IaC using CloudFormation: now Greengrass groups and cloud-backed infrastructure can be extracted in one click</li><li>Out-of-box components, so-called Connectors, that facilitate using GPIO, image recognition, security, seamless integration with AWS cloud services</li><li>Some other features that give more power and flexibility to running Lambdas at the edge</li></ul><p>This workshop will provide an overview of key principles of this toolkit, pay special attention to the new features and show a hands-on demo of how all these components work together.</p><h3><strong>Speaker</strong></h3><p>Dmytro Mantula, Solution Architect, Kyiv, Ukraine.</p><h3><strong>When</strong></h3><p>Thursday, July 11th, 2019</p><ul><li>USA 9:30–10:30 AM (PDT) /12:30–1:30 PM (EST)</li><li>Ukraine 6:30–7:30 PM (EEST)</li><li>India 10:00- 11:00 PM (IST)</li><li>Argentina 1:30–2:30 PM (ART)</li><li>Poland, Slovakia 5:30–6:30PM (CEST)</li></ul><h3><strong>Registration Details</strong></h3><p><strong>URL — </strong><a href="https://attendee.gotowebinar.com/register/5307284752660769291">https://attendee.gotowebinar.com/register/5307284752660769291</a><br><strong>Webinar ID</strong> — 397–036–947</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2f43f1f2edc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globallogic-cloud-and-devops-blogs/register-for-our-upcoming-webinar-on-aws-greengrass-a2f43f1f2edc">Register for our upcoming webinar on AWS Greengrass!</a> was originally published in <a href="https://medium.com/globallogic-cloud-and-devops-blogs">GlobalLogic Cloud and DevOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The right and the wrong reasons to do this Multi-cloud thing]]></title>
            <link>https://medium.com/globallogic-cloud-and-devops-blogs/do-multi-cloud-for-the-right-reasons-c5da08a40ae4?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5da08a40ae4</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[multi-cloud]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Sat, 02 Mar 2019 06:14:42 GMT</pubDate>
            <atom:updated>2019-04-08T16:27:23.018Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P0l9KhU56EGHXGYvridFKQ.png" /></figure><h3>The right and the wrong reasons to do this Multicloud thing</h3><p>Cloud has become mainstream. The next big trends gaining stream are multicloud and hybrid cloud deployments. Though a lot of enterprises are jumping on the bandwagon, the guidelines on the why are not clear. Nor is the tooling for multicloud management platforms very mature. In this blog, I share some of the current motivations enterprises to adopt multicloud and their pros and cons. I also share recommendations on adopting suitable multicloud strategies.</p><h3>Reason #1 — to avoid vendor lock in</h3><p>This is one of biggest motivators for enterprises. Most enterprises are used to working with traditional hardware and software vendors in a <a href="https://en.wikipedia.org/wiki/Capital_expenditure">CAPEX </a>model, and have generally paid through the nose for expensive equipment, licenses and support cost. While the <a href="https://en.wikipedia.org/wiki/Operating_expense">OPEX </a>model of cloud addresses that to some extent, enterprises are still wary of getting locked into cloud vendors’ specific services for this reason.</p><p>While this is a valid concern, zero lock-in is not a practical goal. It often involves forgoing use of specialized managed services and relegates the cloud platform to an over-sized provider of boxes. It also increases management overhead significantly. Even when container orchestration platforms are used over public cloud, enterprises end up having to manage governance at both layers.</p><blockquote><strong>Recommendation</strong> #1 — Pick a primary cloud provider and use a secondary cloud for data backup and disaster recovery, if needed.</blockquote><p>You can find some thoughts on how to <a href="https://medium.com/globallogic-cloud-and-devops-blogs/clouds-compared-aws-vs-azure-vs-gcp-c59519b9d5e4"><strong>choose the right primary cloud provider for you here</strong></a>.</p><h3>Reason #2 — to mitigate cloud outages</h3><p>In the early days of public cloud, there were often high profile outages with the major cloud platforms. These outages impacted well known Internet business and enterprises. In more recent years, such outages have been greatly reduced, and when happen, they often impact specific services, rather than entire platforms. This is because cloud providers have learned from these incidents and improved resilience and redundancy of their platforms substantially.</p><p>While this does not rule out future outages completely, since these providers operate at hyper-scale, even when outages do happen, they are more likely to respond and fix issues quicker than you would in your private data center. Any learnings get implemented across the platform, so it would be unlikely to see the same issues being repeated.</p><p>Even so, cloud providers recommend that customers use architecture best practices and plan for failure, to reduce any impact on their workloads. This includes using multi-zone and multi-region architectures. Failures can happen at the following levels:</p><ul><li><strong>Server level </strong>— Individual VMs are impacted</li><li><strong>Service level </strong>— One or more services within one or more regions are impacted</li><li><strong>Zone level </strong>— An entire zone within a region goes down</li><li><strong>Region level </strong>— An entire region of a cloud platform goes down</li><li><strong>Platform level</strong> — Entire platform goes down across all regions</li></ul><p>Complete platform level failures are unlikely. But if your business continuity needs demand that this scenario be mitigated, our recommendation is to:</p><blockquote>Recommendation #2 — Pick a primary cloud provider and utilize multi-region architectures</blockquote><blockquote>Also, see Recommendation #1</blockquote><h3>Reason #3 — cost, cost, cost(?)</h3><p>Cost is not really a factor to consider moving to a multicloud approach. We recommend doing an initial comparative <a href="https://en.wikipedia.org/wiki/Total_cost_of_ownership">TCO </a>analysis to figure out which cloud platform would be the most suitable and cost effective as the primary cloud platform. Cloud providers are very helpful in providing solutioning and migration support to get your workloads on their platforms. So it helps to talk to your account managers and understand the benefits they can provide.</p><p>For large workloads, further negotiations can be done with the chosen cloud provider. Usually, customers with over $5 million annual cloud spend can negotiate with cloud providers for custom discounts.</p><blockquote>Recommendation #3 — Stick with one cloud and work with your chosen cloud provider on how they can help you.</blockquote><h3>Reason #4 — Oh, but those fancy services!</h3><p>In my opinion, this is the best reason to adopt a multicloud approach. In this case, enterprises can choose a primary cloud provider that meets a majority of their needs. Additional workloads that fit or require services from other cloud providers can be deployed to respective clouds.</p><p>Enterprises will still need to integrate access control (<a href="https://en.wikipedia.org/wiki/Identity_management">IAM</a>), monitoring and policies across the platforms. However, since they’re only pushing specific workloads to additional clouds, the spread would be smaller and more manageable. Use of <a href="https://en.wikipedia.org/wiki/Single_sign-on">SSO</a>, cloud management platforms (<a href="https://searchcloudcomputing.techtarget.com/definition/Cloud-management-platform">CMP</a>), cost management solutions is recommended.</p><blockquote>Recommendation #4 — Choose the primary cloud based on the platform services you need. Utilize services on other clouds when necessary.</blockquote><blockquote>Recommendation #5 — Don’t forget the use of appropriate tools for managing cost, policy and operations.</blockquote><h3>Do’s and Don’ts</h3><ul><li>Use platform provided managed services if they exist and fit functional and performance requirements.</li><li>Use containers where you don’t need platform managed services.</li><li>Consider cost of operating a multicloud landscape, including tools and multicloud literate staff (which are harder to find).</li><li>Use cost, security and cost management tools that support your target cloud platforms.</li><li>Implement overlay networking, access control (IAM) and enterprise policies.</li><li>Use third party tools for <a href="https://whatis.techtarget.com/definition/IT-chargeback-system">chargeback </a>reconciliation.</li><li>Unifying budgeting and cost management across billing and discount models is challenging. Here’s where cloud management tools come in, and can help, but they are not necessarily a silver bullet, as functionalities across clouds can vary significantly</li></ul><h3>Summary</h3><p>While the buzz around multicloud is reaching fever pitch, we recommend and advise to be driven by their specific requirements, rather than just going by the professed benefits of multicloud. In some cases, multicloud may not be a required.</p><p>We’ve seen some of our customers go all in on a single cloud platform. This allows them to negotiate substantial discounts with cloud providers and get consulting and solutioning support. While alternative clouds can still be used for disaster recovery and backup, this allows simplification of cloud governance.</p><p>Containers are the go-to strategy for multicloud these days. But it highly recommended to evaluate the right container platform that fits your enterprise’s functional and governance requirements. Most container platforms support one or more clouds. Evaluate compatibility and support before committing to the container + cloud stack. A proof-of-concept exercise is recommended before locking the stack down.</p><p><em>This blog is part of our ongoing cloud series. To find out how GlobalLogic can help in your cloud adoption journey, please reach out to us at </em><a href="/service/mailto:cloud@globallogic.com"><em>cloud@globallogic.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5da08a40ae4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globallogic-cloud-and-devops-blogs/do-multi-cloud-for-the-right-reasons-c5da08a40ae4">The right and the wrong reasons to do this Multi-cloud thing</a> was originally published in <a href="https://medium.com/globallogic-cloud-and-devops-blogs">GlobalLogic Cloud and DevOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Migration Series]]></title>
            <link>https://medium.com/series/cloud-migration-series-fde9415c4f5c?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/fde9415c4f5c</guid>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Thu, 31 Jan 2019 10:04:16 GMT</pubDate>
            <atom:updated>2019-01-31T10:04:16.365Z</atom:updated>
            <content:encoded><![CDATA[<img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fde9415c4f5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clouds Compared — AWS vs Azure vs GCP]]></title>
            <link>https://medium.com/globallogic-cloud-and-devops-blogs/clouds-compared-aws-vs-azure-vs-gcp-c59519b9d5e4?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/c59519b9d5e4</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Fri, 04 Jan 2019 10:24:06 GMT</pubDate>
            <atom:updated>2019-01-31T09:27:37.721Z</atom:updated>
            <content:encoded><![CDATA[<h3>Clouds Compared — AWS vs Azure vs GCP</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*go7sTFOGN2fJGgYrI3E-FA.png" /></figure><p>Public cloud has, in the last few years, broken through the mainstream enterprise consciousness. Even if these enterprises are not betting it all on cloud, cloud adoption is, in one form or the other, an integral part of most enterprises’ infrastructure strategy and roadmap. For enterprises who are about to embark on this journey, the questions being asked are, “Which cloud platform should I adopt?”, “Which cloud platform provides cost effective services that are a fit for me?”, and “How do I go about my cloud adoption journey?” This blog attempts to answer the first two questions.</p><p>To that goal, I have compared the core infrastructure services across the most popular cloud providers, which are Amazon Web Services (AWS), Microsoft Azure and Google Cloud Platform (GCP). In addition to the core infrastructure services, each cloud provider brings their unique proprietary offerings in the NoSQL, Big Data, Analytics, ML and other such areas.</p><p>This blog calls out each cloud’s unique aspects that may influence an enterprise’s choice of cloud based on their specific business and technical requirements.</p><h3>Amazon Web Services (AWS)</h3><p>AWS is the oldest public cloud provider with the widest range of products, compute and data storage options and managed services. AWS Marketplace is also the largest marketplace for third party applications and appliances. They also rapidly iterate to continuously add a substantial set of product features. Highly driven by customer feedback, their new services provide close integration with their core services like IAM, KMS etc. They have a strong focus on security and architecture best practices. Their enterprise frameworks such as the Well-Architected Framework and Cloud Adoption Framework have been developed from their experience with large enterprise customers. Besides their mainstream services, they are also known to release unconventional services as SnowMobile (data transfer appliance in a truck), RoboMaker (robotics framework) and Ground Station-as-a-Service (for managed satellite data download). This keeps customer interest piqued and has potential to open up entire industries. Their 51% market share is a proof of that. That said, they aren’t the cheapest cloud on the market. They also don’t seem to be worried about providing deeper container offerings. Their EKS (managed Kubernetes) service was relatively late to the market. Instead, they seem to be placing bets on MicroVMs (Firecracker) and managed functions.</p><p>They have lately seem to realign their focus towards hybrid cloud, and have announced offerings such as Outposts, (in partnership with VMware) that will enable customers to use well known AWS services and APIs on infra running in their private data centers.</p><h4>When to choose AWS</h4><p>AWS is a great choice for startups and enterprises alike. From web and analytical workloads, to large scale data center migrations, AWS provides a breath of services that customers can leverage. To help get customers of all shapes and sizes started on the platform, AWS has released supposedly niche services such as RoboMaker on one end, while going backwards to build services such as LightSail (virtual private server) to help even the smallest single server workloads be onboarded without much overhead.</p><p>When it comes to compute, AWS provides the widest range of VM types. AWS also currently has the highest compute and storage options available in the market. Their wide range of VM types (136 VM types over 26 VM families) enable customers to run everything from small web workloads to the biggest HPC and SAP workloads.</p><p>For machine learning and AI workloads, AWS also provides the highest configurations of GPU enabled VM types. For workloads that require single tenancy for compliance and regulatory reasons, AWS also now provides Bare-Metal-as-a-Service. For virtualized workloads that might need it, AWS provides features such as placement groups to ensure that the workloads run on a designated underlying hardware.</p><p>AWS hopes that the various t-shirt VM sizes will match your workload requirements. It therefore doesn’t support creation of custom VM sizes (vCPU, RAM). Unlike other cloud providers (CSPs), it only provides a specific set of VM families which come with GPUs. It does not allow attaching GPUs to any or all VM types in its portfolio.</p><p>Block storage comes with a variety of options, such as dynamic resizing, different disk types (magnetic and SSD). Unlike other CSPs, AWS does not restrict IOPS by volume size. You can provision IOPS at extra charge to even small disks.</p><p>On the managed relational database front, AWS supports managed databases for MySQL, PostgreSQL, MariaDB, Oracle (both SE and EE) and MS SQL (Web and Enterprise editions) under their RDS offering. In addition, they have their own MySQL and PostgreSQL compatible database offering that boasts Oracle like performance at fraction of the cost. They are investing in this heavily and have also announced Multi-Master and Serverless versions.</p><p>For NoSQL databases, AWS has had their DynamoDB product available for over half a decade. This evolved from their SimpleDB offering. AWS is a proponent of and provides a range of purpose-built NoSQL databases. These include, DynamoDB (key value and document), Neptune (Graph), and Elasticache (key value caching).</p><p>AWS has improved its networking services portfolio over the last decade. It started with VPC and related network features such as security groups, network ACLs and Internet Gateways. At the time, users still had to configure their own NAT servers, bastion hosts etc. AWS has listened to customer feedback and gradually added these as managed network services to its portfolio. AWS now provides a managed NAT gateway, VPN Gateway, Transit Gateway, Direct Connect Gateway etc. They recently also announced a managed Client VPN service. This removes the need for customers to deploy OpenVPN servers to manage access to cloud VMs.</p><p>For network security, AWS has launched managed services for DDoS protection (AWS Shield) and Web Application Firewall (WAF), along with AWS Inspector, AWS Config and CloudTrail for inventory and policy management and auditing. GuardDuty provides threat detection.</p><p>For data security, AWS provides encryption at rest for most of its storage services. AWS also has KMS and CloudHSM services for key management. Macie provides an AI driven data loss prevention (DLP) service.</p><p>On the queueing, messaging and notification front, AWS provides managed AMQP compatible queue service (Amazon MQ) in addition to its SQS offering. For Pub/Sub, AWS has offered Kinesis and has recently added a managed Kafka offering. SNS provides a multi-channel integrated notification services that allows customer notifications over SMS, mobile, SMS and email notifications. Internally, it also connects with its other services to enable event driven loosely coupled architectures.</p><p>AWS serves US Government workloads in separate GovCloud regions in the US. Customers who need to provide services to customers in China can rely on AWS’s China region, which is provided via partnership with third party providers.</p><p>All in all AWS provides a breadth and depth of services and features that are suitable for a substantial number of enterprises.</p><h3>Microsoft Azure</h3><p>Microsoft had lagged behind AWS in the public cloud game, but it focused first on SaaS and PaaS offerings as its strengths lie in both enterprise and consumer software. Microsoft initially focused on PaaS services for Azure. These were focused on their existing base of Microsoft developers. Over time, Microsoft expanded focus to both Linux and IaaS services. This also reflected in their re-branding Azure from <strong><em>Windows Azure</em></strong> to <strong><em>Microsoft Azure</em></strong>, and <strong><em>Microsoft loves Linux</em></strong> campaigns. Over time, Microsoft has also made Azure more startup friendly and built out API support for its various services. However, despite the breadth of its services, Microsoft lags substantially behind AWS in enterprise adoption. Large enterprises that already have existing Microsoft relationships remain a large part of the user base, though Azure is seeing robust growth in year-on-year revenue.</p><h4>When to choose Azure</h4><p>Azure is a mature cloud platform with a breadth of features which may be a preferred platform for customers that are already using Microsoft products in some way. While Azure supports a number of open source product based services, the Microsoft portfolio on cloud is what sets it apart for customers.</p><p>Azure has over 151 VM types over 26 VM families that support everything from small web workloads to the HPC, Oracle and SAP workloads. Azure has both Windows and multiple flavors of Linux (RHEL, CentOS, SUSE, Ubuntu). Azure has a separate family of instances for ML/AI workloads.</p><p>If you need to run high-end workloads that require up to 128 vCPU and 3.5 TB memory, Azure is a good bet. If you have existing licenses for windows OS, MS-SQL and bring them to cloud (BYOL) via Microsoft License Mobility Program, Azure is the cloud to choose. License costs form a substantial part of infrastructure expenses, and will be a major consideration for customers who run large deployments of MS-SQL etc.</p><p>Azure was also the first cloud player to recognize the trend towards hybrid cloud, and had one of the first hybrid cloud and Cloud-in-your-Datacenter offering (Azure Stack). Customers who wanted the interface of Azure but wanted to run services in their own data centers could use Azure Stack. Other cloud players are only catching up with Azure in this space. Azure also provided support for hybrid storage appliances like StorSimple, which was unique in the public cloud space.</p><p>If you have a data center with predominantly Microsoft workloads and need to do a large scale data center migration to cloud, while taking advantage of familiar tools, Azure provides tooling and services, such as Azure Site Recovery.</p><p>When it comes to SQL and NoSQL databases, Azure has a fairly well rounded set of services. It provides managed MS SQL Server and SQL Datawarehouse. Azure also provides managed databases for MySQL, PostgreSQL, and MariaDB. Azure Table is a managed key value store, whereas CosmosDB provides multi-model, globally distributed NoSQL database with multiple consistency models. It provides an API compatible with MongoDB, Cassandra, Gremlin (Graph) and Azure Table Storage. If you need to run multiple managed data models, including document, graph, key-value, table, and column-family data models in a single cloud, Cosmos may be the way to go. Azure cache for Redis rounds off the offerings with a managed cache.</p><p>In addition to PAYG billing model with credit card and invoicing modes, customers with existing enterprise accounts may pre-purchase Azure subscriptions as part of their annual renewals. This is useful for customers who want to be able to budget the annual cloud spend upfront. This prevents the uncertainty and additional mid-year budget approvals that are usually associated with PAYG models. When doing this, enterprises should size their projected workloads with some accuracy so that no pre-paid credits are wasted at the end of the year.</p><p>License mobility to cloud for Microsoft products is also relatively easy for customers with multiple Microsoft products running on-prem.</p><h3>Google Cloud Platform (GCP)</h3><p>Google Cloud Platform (GCP), while late to the game and having the smallest market share of the public cloud providers compared here (current market share at about 4%), is showing a robust percentage growth. It boasts of several features that put it ahead of its competitors in certain areas. GCP is also riding the wave not only new customers who are already part of the ecosystem, but also early cloud adopters who are looking to expand their landscape to Google as part of a multi-cloud strategy. Google also started with PaaS services but has been steadily expanding its product portfolio.</p><p>Along with innovative features, Google boasts the lowest list price on infrastructure compared to all the other cloud providers. Of course, total expenditure for any enterprise depends on services used and cost governance measures in place.</p><h4>When to choose GCP</h4><p>From a compute perspective, Google has the smallest number of t-shirt VM sizes (28 instance types over 4 categories). However, it has one feature which makes these numbers slightly irrelevant. Google allows users to create their own custom sizes (CPU, memory) so that customers can match their cloud workloads sizing to their on-prem sizing. They also bill customers based on the total CPU and memory used, rather than individual VMs. This reduces wastage of unused capacity.</p><p>Another unique feature is that GCP allows almost all instance types to attach GPUs. This can turn any standard or custom instance into a ML ready VM. Google was also a leader in per-second billing, which forced other CSPs to follow suit. Compared to the pervious norm of per hour billing, per-second billing greatly reduces any capacity wastage. This results in up to a 40% savings overall, compared to relying on standard VM t-shirt sizes and per hour billing.</p><p>VM startup times in GCP are phenomenally fast, and leave other CSPs in the dust. This makes scaling out especially responsive. GCP also allows dynamic resizing of disks, so that you don’t have to do sysops acrobatics when your disks fill up. IOPS are assigned based on disk sizes and cannot be provisioned separately. This might be problematic for customers who want high IOPS on a small data set, and result on wasted dollars for unwanted storage.</p><p>Google has also tied up with or purchased third party cloud migration tools. These tools, such as CloudEndure, Velostrata and CloudPhysics, help customers assess, plan and live-migrate their VMs to GCP essentially for free. On other cloud providers, some of these tools cost several hundred dollars per VM. Google is clearly making migration to GCP as easy as possible.</p><p>Networking is where GCP shines. They have a global low latency network. Even from customer perspective, a VPC network spans all their regions. Other CSPs limit VPC networks to a region. This makes it easy for GCP customers to build applications that serve customers globally, without building complex cross region infrastructure design and data replication mechanisms.</p><p>Object storage also supports a multi-regional mode, where data is replicated across regions automatically. For customers considering a migration from AWS, or considering a multi-cloud strategy, GCP supports importing object storage from AWS.</p><p>For relational databases, GCP provides support for managed MySQL and PostgreSQL databases. For customers who want a globally distributed database that still supports immediate consistency and ACID properties, GCP has built Spanner. Spanner uses consensus algorithms and atomic clocks to synchronize transactions between nodes. This offering is unique to GCP and makes Spanner very attractive to large enterprise customers who have these requirements from their relational data store. In fact, another open source database, CockroachDB, is based on the Spanner paper that was published by Google.</p><p>From a NoSQL perspective, GCP has a product called BigTable. BigTable is a petabyte scale, managed wide-column NoSQL database that is used by Google in its own products such as Gmail.</p><p>From a billing perspective, Google provides automatic discounts such as sustained use discounts which reduce the on-demand price if a VM runs more than a certain number of hours in a month. If you want the most cost effective cloud provider in the market today, GCP is a good choice.</p><p>While it may not have the sheer depth of features of some of the other CSPs, it has some unique products in its portfolio, and is an attractive option being a price leader in the market.</p><h3>Conclusion and Future Outlook</h3><p>As detailed above, each cloud has features and advantages that appeal to specific customer needs. While all the cloud providers will continue to provide certain common services (such as managed MySQL database), each CSP will continue to build out unique, differentiated services (e.g. Aurora, Cosmos, Spanner) that are purpose built to solve very specific customer needs. CSPs hope that this will increase customer stickiness and create a lock in.</p><p>From a customer perspective, these services will also become a driver to adopt a multi-cloud strategy. As an example, a customer might likely want to use GCP for one app that needs Spanner’s features, while they use AWS for their AI services, and Azure for specific Windows workloads.</p><p>Even for future looking services like computer vision and speech recognition, customer needs might drive them to mix and match services across cloud platforms, to meet their application’s requirements. Customer will likely use one cloud as their primary platform, while using services from others for specific applications.</p><p><em>This blog is part of our ongoing cloud series. To find out how GlobalLogic can help in your cloud adoption journey, please reach out to us at </em><a href="/service/mailto:cloud@globallogic.com"><em>cloud@globallogic.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c59519b9d5e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globallogic-cloud-and-devops-blogs/clouds-compared-aws-vs-azure-vs-gcp-c59519b9d5e4">Clouds Compared — AWS vs Azure vs GCP</a> was originally published in <a href="https://medium.com/globallogic-cloud-and-devops-blogs">GlobalLogic Cloud and DevOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Migration — Assessment Factors]]></title>
            <link>https://medium.com/globallogic-cloud-and-devops-blogs/cloud-migration-assessment-factors-2d49747f45df?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d49747f45df</guid>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-assessment]]></category>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Mon, 16 Jul 2018 16:54:51 GMT</pubDate>
            <atom:updated>2018-07-17T17:33:46.123Z</atom:updated>
            <content:encoded><![CDATA[<p>During the migration assessment phase, there are several factors to consider, which impact migration feasibility and strategy.</p><p>The goal of doing a migration assessment is to:</p><ol><li>Figure out the feasibility of migrating an application to the cloud.</li><li>Understand the <a href="https://medium.com/globallogic-cloud-and-devops-blogs/drivers-for-cloud-migration-ffd647647feb"><strong>migration drivers</strong></a></li><li>Migration strategy that can be used (infrastructure and data)</li><li>The resource requirements for the cloud</li><li>Understand application up-time and DR constraints</li><li>Identify business and operational risks</li></ol><p>We describe a few critical assessment factors and their impacts below:</p><h3>Compute</h3><h4><strong>Assessment Factors</strong></h4><ul><li>Is the workload running on bare metal or a virtualization platform?</li><li>Is the workload running on an x86 system?</li><li>How many roles running in how many servers/VMs?</li><li>Does the application use any custom hardware appliances?</li></ul><h4>Impact</h4><p>Cloud platforms are predominantly based on x86 hardware. These answers help decide if the workloads are compatible with the target cloud platform.</p><h3>Storage</h3><h4>Assessment Factors</h4><ul><li>Is there a shared or clustered storage used by the application?</li><li>Is there any NFS storage used by the application?</li><li>Is the storage being provided by a SAN?</li></ul><h4>Impact</h4><p>Features such as shared storage are not available on cloud platforms. This usually requires a workaround such as virtual NAS appliances.</p><h3>Networking</h3><h4>Assessment Factors</h4><ul><li>What firewalls are used for the workload?</li><li>Does the workload use IP multicast or broadcast?</li><li>How are the subnets designed?</li><li>Does the application use Load balancers?</li></ul><h4>Impact</h4><p>IP Multicast often used for media applications but not supported on cloud platforms. This is to keep the networking control plane simple and manageable.</p><h3>Application</h3><h4>Assessment Factors</h4><ul><li>What type of application is it (public facing, corporate, analytics, etc.)?</li><li>Is the application in-house or purchased from a vendor (traditional COTS)?</li><li>If purchased, does the application vendor have a SaaS offering (such as O365)?</li><li>Is the application stateless or stateful (for web applications)?</li></ul><h4>Impact</h4><p>Availability of SaaS alternatives impacts migration path. If an commercially available SaaS application provides a good alternative for an existing application, then the effort of migrating that application to the cloud can be avoided. For example, existing Microsoft Exchange deployments can be replaced with Office365 subscriptions, instead of migrating Exchange servers to the cloud.</p><h3>Licenses</h3><h4>Assessment Factors</h4><ul><li>Does the application use commercial or licensed software?</li><li>If yes, are the licenses portable to cloud?</li><li>Is there a managed version of the software on cloud?</li><li>Is there an open source equivalent of the software on cloud?</li></ul><h4>Impact</h4><p>Impacts choice between BYOL or Pay-As-You-Go versions and associated costs.</p><h3>Security</h3><h4>Assessment Factors</h4><ul><li>Does the application use HSMs or any other corporate key management solution?</li><li>Is the application tied to the local MAC IDs of the underlying hardware?</li><li>Does the application use a Active Directory, or a corporate or third party SSO service?</li><li>Is data encrypted at rest? If yes, what mechanisms are used?</li><li>Is data encrypted when being served to end user?</li><li>Is data encrypted between servers within the application?</li><li>Does the application need to comply to a regulatory standard such as PCI-DSS, GDPR, etc.?</li></ul><h4>Impact</h4><p>Hardware appliances cannot be migrated to the cloud, whereas tight coupling between the application and underlying hardware may constrain the migration. If virtual appliances are not available to replace the on premises hardware, hybrid environment may be a good intermediate stage for the migration. In this case, the hardware components stay on-prem, while others are migrated.</p><h3>Availability and Disaster Recovery</h3><h4>Assessment Factors</h4><ul><li>Is the application designed for HA?</li><li>What kind of uptime constraints does the workload have?</li><li>What is the RTO and RPO for the application?</li></ul><h4>Impact</h4><ul><li>Uptime constraints impact cloud architecture and migration strategy</li><li>RTO and RPO impact DR planning and strategies</li></ul><h3>Application and Operations Support</h3><h4>Assessment Factors</h4><ul><li>Are there any CI/CD or DevOps processes in place?</li><li>Does the application have ongoing development support?</li><li>Does the operations team have necessary cloud skills?</li></ul><h4>Impact</h4><p>Dev support can support refactoring if app needs small modifications.</p><p>The combination of the above factors decide how an application is taken to the cloud. In future posts, we’ll talk about some migration paths such as lift-and-shift.</p><p><em>This blog is part of our ongoing cloud series. To find out how GlobalLogic can help in your cloud migration journey, please reach out to us at </em><a href="/service/mailto:cloud@globallogic.com"><em>cloud@globallogic.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d49747f45df" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globallogic-cloud-and-devops-blogs/cloud-migration-assessment-factors-2d49747f45df">Cloud Migration — Assessment Factors</a> was originally published in <a href="https://medium.com/globallogic-cloud-and-devops-blogs">GlobalLogic Cloud and DevOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud migration — Strategies and applicability]]></title>
            <link>https://medium.com/globallogic-cloud-and-devops-blogs/cloud-migration-strategies-and-applicability-f0661c1ee35f?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0661c1ee35f</guid>
            <category><![CDATA[lift-and-shift]]></category>
            <category><![CDATA[cloud-strategy]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Wed, 11 Jul 2018 15:25:00 GMT</pubDate>
            <atom:updated>2018-07-11T15:25:00.781Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog describes the various cloud migration strategies and cases where each strategy is useful</p><p>Stephen Orban’s blog on <a href="https://medium.com/aws-enterprise-collection/6-strategies-for-migrating-applications-to-the-cloud-eb4e85c412b4"><strong><em>6 strategies for migrating applications to cloud</em></strong></a> is the most definitive description of the various approaches that an enterprise can adopt for migration. In this blog, we talk about the pros, cons, applicability and the “how-to” that is associated with each of these strategies.</p><h3>Rehost (or Lift and Shift)</h3><p>This strategy is used to redeploy applications as-is to a cloud infrastructure and change the application’s infrastructure configuration.</p><h4>Pros</h4><ul><li>Short migration path (a few weeks to a few months)</li><li>Suitable for bulk/data center migrations</li><li>Immediate cost savings compared to on-premises infrastructure</li></ul><h4>Cons</h4><ul><li>Doesn’t utilize cloud native features such as elasticity</li></ul><h4>Applicability</h4><ul><li>When time is a constraint (see drivers for cloud migration)</li><li>Legacy apps that cannot be immediately modernized</li><li>No AppDev and DevOps capability or bandwidth</li></ul><h4>Approaches</h4><ul><li>Backup and Restore VM and Data</li><li>Fresh Install (recreate VMs and migrate data)</li><li>Live Migration (using tools like CloudEndure)</li></ul><h3>Replatform</h3><p>This strategy is used when applications or selective components of an application are migrated to a cloud’s compatible PaaS services (such as managed Databases such as RDS or CloudSQL, or PaaS services such as AWS Elastic Beanstalk, etc.), without any changes to the application code.</p><h4>Pros</h4><ul><li>Applications can quickly start to see benefits of cloud managed components without a full refactoring/re-architecting cycle</li><li>Quick migration path (a few weeks to a few months)</li><li>Reduces operational load on the SysOps teams</li></ul><h4>Cons</h4><ul><li>Usually an intermediate stage before a full refactoring exercise</li><li>Applications may not be ready for web-scale elasticity till a full refactoring exercise</li><li>Possible early lock-in with PaaS services. May be difficult to migrate out of them</li></ul><h4>Applicability</h4><ul><li>Suitable for fairly decoupled n-tier applications</li><li>When time is a constraint (see my blog, <a href="https://medium.com/globallogic-cloud-and-devops-blogs/drivers-for-cloud-migration-ffd647647feb"><strong><em>drivers for cloud migration</em></strong></a>)</li></ul><h4>Approaches</h4><ul><li>Move one or more applicable tiers to PaaS services, while rehosting (lift-and-shift) the remaining components.</li></ul><h3>Refactor</h3><p>This approach is used when an enterprise is undergoing a digital transformation. During this exercise, enterprises usually refactor (or re-architect, rebuilt) existing solutions or rewrite applications from scratch, to take full advantage of a modern PaaS or serverless cloud architectures and cloud services. This exercise requires a full development cycle and optionally, adoption of DevOps culture before an application can be migrated to cloud.</p><h4>Pros</h4><ul><li>Achieves the best of both worlds in terms of cloud architecture and DevOps best practices</li><li>Automation focused with Infrastructure-as-Code principles</li></ul><h4>Cons</h4><ul><li>The longest path to migration</li><li>Often dependent on successful adoption of DevOps practices</li><li>Possible lock-in with PaaS services. Customers looking at container solutions to workaround these problems</li></ul><h4>Applicability</h4><ul><li>When the focus is on modernizing an application based on new business flows.</li><li>When there is a focus on adoption of a DevOps culture.</li><li>New (greenfield) applications</li></ul><h4>Approaches</h4><ul><li>Full development lifecycle, often accompanied by adoption of DevOps culture</li><li>Full data modeling and migration</li></ul><h3>Replace</h3><p>This strategy is used when an enterprise chooses to replace in-house software with an equivalent SaaS service.</p><h4>Pros</h4><ul><li>Move from an in-house to a fully managed solution</li><li>Future feature updates and data migration is handled by SaaS vendor</li><li>OPEX based (often, per user) billing models</li><li>No development teams required for app modernization (data management teams required for data migration to SaaS platform)</li></ul><h4>Cons</h4><ul><li>Possible data mapping and export issues</li><li>Migrations for large enterprises can involve longer timeframes. Maintaining data consistency in this hybrid scenario can be a challenge.</li><li>Vendor lock-in once migrated</li></ul><h4>Applicability</h4><ul><li>In-house or licensed legacy software where industry leading SaaS platforms provide a managed and cost effective option and provide most or all of the required functionality.</li><li>For e.g. — MS Exchange deployments are often replaced with Office 365. In-house SFA and CRM tools can be replaced with platforms like SalesForce.</li></ul><h4>Approaches</h4><ul><li>Identify and map data schemas and plan phased data migration</li></ul><h3>Retire</h3><p>This happens often when there are multiple versions of legacy software running on-premises and older versions are either being or have been phased out but still hosted. A migration readiness assessment can help identify such applications.</p><h4>Pros</h4><ul><li>Consolidated infrastructure footprint in the cloud</li></ul><h4>Cons</h4><ul><li>None</li></ul><h4>Applicability</h4><ul><li>Older versions of applications that are no longer in use.</li></ul><h4>Approaches</h4><ul><li>Decommission application and backup and data for compliance if needed.</li></ul><p><em>This blog is part of our ongoing cloud series. To find out how GlobalLogic can help in your cloud migration journey, please reach out to us at </em><a href="/service/mailto:cloud@globallogic.com"><em>cloud@globallogic.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0661c1ee35f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globallogic-cloud-and-devops-blogs/cloud-migration-strategies-and-applicability-f0661c1ee35f">Cloud migration — Strategies and applicability</a> was originally published in <a href="https://medium.com/globallogic-cloud-and-devops-blogs">GlobalLogic Cloud and DevOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cost management challenges in the cloud]]></title>
            <link>https://medium.com/globallogic-cloud-and-devops-blogs/cost-management-challenges-in-the-cloud-532145ca0d0c?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/532145ca0d0c</guid>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[cloud-governance]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-tco]]></category>
            <category><![CDATA[cloud-cost-management]]></category>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Mon, 09 Jul 2018 11:36:31 GMT</pubDate>
            <atom:updated>2018-07-10T11:29:05.327Z</atom:updated>
            <content:encoded><![CDATA[<p>When it comes to cloud cost control, these are some of the big challenges enterprises face.</p><p>Cloud adoption is no longer an if. Instead, more and more enterprises are asking the question, what (to move to the cloud) when (to move it) and how (to choose the right architecture and services).</p><p>From the cost perspective, there are four phases of a typical lifecycle that a workload goes through and the key questions that should be asked during each of these phases:</p><h4><strong>Planning</strong></h4><ul><li>What cloud resources do I need?</li><li>Who should be able to create them?</li><li>How much should it cost?</li><li>Who owns the cloud budget for the applications?</li></ul><h4><strong>Migration</strong></h4><ul><li>Have I considered cloud costs before and after Go-Live for each application?</li><li>Have I taken into account the migration plan for my budget?</li><li>Have I benchmarked my cloud architecture to validate the initial sizing and budgets?</li></ul><h4><strong>Operations</strong></h4><ul><li>How much am I spending on each application?</li><li>Is it in line with my expected budget?</li><li>Are there any surprises?</li></ul><h4><strong>Optimization</strong></h4><ul><li>Am I using my resources in the most efficient manner?</li><li>Am I utilizing cloud features to reduce cost?</li><li>Can I control costs as my apps evolve?</li></ul><p>However, As enterprises move more and more workloads to the cloud, they often miss out on addressing these questions, resulting in a situation commonly called the <strong><em>cloud sprawl</em></strong>.</p><p>At this point, the enterprise usually would have lost visibility and control on their cloud landscape and costs, and start to see (often substantial) cost overruns. Let’s deep dive into some of the reasons why this happens:</p><h3><strong>Cost Ownership</strong></h3><p>This is a key challenge. To utilize the full benefits of the speed and agility that cloud provides, modern IT usually provides a common services framework, wherein the business teams are allowed to manage the cloud resources for their applications themselves. While this is the recommended practice, cost ownership often falls through the cracks. We’ve seen customer situations where IT creates accounts and projects for business teams to use, and then hands them over to the business teams, but still owns the costing and billing.</p><p>What results from this arrangement is that the business teams get a free reign to create resources, which they do, often well outside of their allocated budgets. They are also neither aware and often not bothered with the mounting spends since they are not the ones footing the bill.</p><p>This is usually made worse with the fact that IT does not have strong cost reporting mechanisms to bring visibility into the who and what of the budget overruns.</p><h3><strong>Budgets and TCO</strong></h3><p>Doing an initial cloud TCO is absolutely essential to arrive at a budget for your cloud landscape. When this is done done, stakeholders have no visibility into what their infrastructure is going to cost. Cost saving is often one of the big reasons for cloud adoption, but not doing this exercise results in a bill shock to the enterprise and often takes the steam out of the cloud adoption momentum.</p><p>Even when enterprises do a TCO exercise, they often do the TCO for the final production landscape. They sometimes miss taking into account the migration plan, DevOps processes and Go-Live dates, and also do not sufficiently size for them. This causes situations where costs skyrocket even before the application is fully migrated. Dev/Test environments tend to severely bloat up and eat into the overall budget.</p><h3><strong>Visibility</strong></h3><p>Even when enterprises have done initial sizing and defined cost ownership, having day to day visibility into the cost is important. Because it’s very easy to create resources in the cloud (within minutes), waste becomes a concern. Resources may be created for temporary use but never shut down. We have also seen situations where hackers have obtained access to customers’ cloud accounts and created hundreds of servers. The problems with lack of visibility can be summarized as below:</p><ul><li>Stakeholders do not have granular visibility and actionable insights into their cloud landscape</li><li>Continuous monitoring not in place, resulting in month-end bill shocks</li><li>Projections on cloud utilization trends not available</li></ul><h3><strong>Governance</strong></h3><p>Building the correct cost governance is a key pillar of the overall cloud governance framework. Problems occur when some of the following governance structures are not put into place:</p><ul><li><strong>Tagging and labeling strategy</strong> is required for both automation and charge-back/show-back. When a comprehensive tagging strategy is missing, it gets very difficult to do a deep dive into billing data to identify which applications resources belong to and who created them.</li><li><strong>Enterprise level access control and provisioning policies</strong>, when not clearly defined and enforced for cloud, result in unauthorized actors to create resources. Controlling who can create what resources is essential to manage the cloud sprawl.</li><li><strong>Cloud governance requires behavioral change</strong> across organizations. Enterprises that try to retrofit existing processes that work on-premises to the cloud, will lose the advantage that come with it. On the other hand, moving to cloud without training the various stakeholders on the new governance models also result in lapses and corresponding loss in visibility and tracking.</li></ul><h3><strong>Automation</strong></h3><p>Even when governance models are defined, for large landscapes, enforcing governance manually comes close to not enforcing it at all (<em>imagine the labor involved in tagging 1000 VMs manually</em>). When tools and automation strategies are not used and applied across the entire cloud landscape, IT teams always play catch up and endure a lot of manual work to keep the landscape in shape.</p><p>Similarly, when cost management and remediation tools are not used, manual compliance, cost reporting and optimization become simply untenable, and are often abandoned.</p><h3><strong>Optimization</strong></h3><p>Public clouds are evolving fast. They already provide innovative features like autoscaling, that are not available in on-premises environments. In addition, they provide innovative costing models, and multiple discount options.</p><p>Lastly, they come up with new managed services that not only allow the customer to pay only for what they use, but also lift the management overhead for these services. Enterprises miss out on these benefits when:</p><ul><li>Apps don’t utilize cloud features to optimize cost (e.g. autoscaling)</li><li>Enterprises don’t use Cloud platform discounts</li><li>Enterprises don’t do periodic reviews for validating evolving application architectures</li></ul><p>In future blogs, we’ll talk about building a comprehensive cloud cost management framework to address these issues.</p><p><em>This blog was written with </em><a href="https://medium.com/@faisal.mushtaq"><strong><em>Faisal Mushtaq</em></strong></a><em> and was originally published on the </em><a href="https://www.globallogic.com/blogs/"><em>GlobalLogic web site</em></a><em> as part of our ongoing cloud series. To find out how GlobalLogic can help in your cloud migration journey, please reach out to us at </em><a href="/service/mailto:cloud@globallogic.com"><em>cloud@globallogic.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=532145ca0d0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globallogic-cloud-and-devops-blogs/cost-management-challenges-in-the-cloud-532145ca0d0c">Cost management challenges in the cloud</a> was originally published in <a href="https://medium.com/globallogic-cloud-and-devops-blogs">GlobalLogic Cloud and DevOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Migration — Lift & Shift, or Containerization?]]></title>
            <link>https://medium.com/globallogic-cloud-and-devops-blogs/cloud-migration-lift-shift-or-containerization-d126953b0bc1?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/d126953b0bc1</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[containerization]]></category>
            <category><![CDATA[lift-and-shift]]></category>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Sat, 07 Jul 2018 09:08:41 GMT</pubDate>
            <atom:updated>2018-07-10T11:29:23.434Z</atom:updated>
            <content:encoded><![CDATA[<p>How to decide between containerization and VM migration.</p><p>Many enterprises are evaluating containers and PaaS platforms as their preferred paths to cloud. These are certainly attractive options, but there are a few factors to consider when making a choice between PaaS/Containers and infrastructure to cloud:</p><ul><li><strong>Urgency of migration </strong>— Containerization and DevOps implementation require at least some of sort of implementation effort and time. If there are hard deadlines on migration, then containerization may not be a good strategy.</li><li><strong>Availability of skills on DevOps and Containers</strong> — Containerization and DevOps implementations often go hand in hand. An enterprise may not have these skills available in house to drive this effort. However, some cloud migration paths (such as Lift and Shift) are easier for traditional IT teams to adopt.</li><li><strong>Greenfield vs Legacy apps</strong> — Adopting container and PaaS services is easier when an application is being built ground up. For legacy applications, infrastructure migration may be a better choice.</li><li><strong>Current state of DevOps and container adoption in the organization </strong>— If an enterprise is adopting container and PaaS strategy enterprise-wide, then it is more likely that the technical and operational processes, platforms and skills are in place to handle containerization.</li><li><strong>Enterprise’s attitude towards cloud lock-in</strong> — Containers and PaaS are also often a way for some enterprises to avoid getting locked into one cloud platform. Whereas, other enterprises commit to a single platform wholeheartedly, based on either the business relationship, or the alignment between platform features and enterprise requirements (For example, a traditional Microsoft shop is more likely to choose Azure as their preferred cloud platform). For the latter, directly using cloud services may be a more cost effective option.</li></ul><p><em>This blog is part of our ongoing cloud series. To find out how GlobalLogic can help in your cloud migration journey, please reach out to us at </em><a href="/service/mailto:cloud@globallogic.com"><em>cloud@globallogic.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d126953b0bc1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globallogic-cloud-and-devops-blogs/cloud-migration-lift-shift-or-containerization-d126953b0bc1">Cloud Migration — Lift &amp; Shift, or Containerization?</a> was originally published in <a href="https://medium.com/globallogic-cloud-and-devops-blogs">GlobalLogic Cloud and DevOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drivers for Cloud Migration]]></title>
            <link>https://medium.com/globallogic-cloud-and-devops-blogs/drivers-for-cloud-migration-ffd647647feb?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffd647647feb</guid>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Thu, 05 Jul 2018 19:26:27 GMT</pubDate>
            <atom:updated>2018-07-10T11:29:44.939Z</atom:updated>
            <content:encoded><![CDATA[<p>The can be many reasons why an enterprise might look at cloud adoption. These range from business drivers such as digital transformation, to operational goals such as cost reduction. Based on our experience with enterprise migrations, we have found that they can be categorized under the categories in the following sections. Note that while these are broad categories, enterprises can have more than one cloud migration driver.</p><h3>Hardware End-of-Life</h3><p>Traditionally, enterprises running their own data centers usually design, size and procure hardware for specific applications based on a Bill of Material (BoM). This includes compute (servers, blades), storage (Direct Attached Storage, SAN), networking (switches, firewalls) and other specialized equipment. Hardware purchased can have a lifespan of 3–5 years. Intel and other chip makers have a tick-tock cycle of 18 months (tick= new generation processor, tock=clock speed improvements). This results in hardware vendors typically releasing new generations of their hardware every 3 years.</p><p>Companies will usually retire and refresh the hardware with the latest generations to take advantage of the performance and efficiency. Such hardware refreshes have to usually be bench-marked and sized in each iteration. Each refresh requires significant CAPEX investment.</p><p>On the other hand, the cloud cost model is purely OPEX based. Customers simply pay for what they use, and can release resources that are not being used. Migrating applications whose hardware is to be retired, is an attractive proposition. It saves enterprises from significant CAPEX expenditures, and allows them to evolve to a more beneficial OPEX model.</p><p>Conversely, if an enterprise has made recent significant CAPEX investments in hardware, the value for migrating these applications to the cloud may be low for the time being. In such cases, enterprises can look at cloud for capacity expansion.</p><h3>Cost Savings</h3><p>Besides the cost savings that can be achieved by moving from a CAPEX to an OPEX model (described in the previous section), there are opportunities for significant cost optimization in day to day operations. When hardware is purchased, it comes with a fixed capacity (compute, storage, networking). Usually, enterprises will size and procure hardware to deal with peak loads. The downside to this is that outside of the peak loads, the hardware is not fully utilized and thus not giving a full ROI.</p><p>Enterprises can use private cloud for capacity management at the application level, but at the data center level, the peak load problem still remains, along with potentially unused capacity.</p><p>Public cloud providers like AWS, Azure and Google, on the other hand provide pay-as-you-go models with minute or (more recently) second level billing models. You only pay for what you need, and release the resources when you no longer need them. There are no upfront investments.</p><p>Besides that, as application load changes, customers can resize (or rather, rightsize) the resources within minutes to match the load. All public cloud providers provide APIs for resource management and operational insights. This means that right-sizing operations such as scaling in, scaling out, up and down can be automated based on system triggers. Concepts like autoscaling allow applications to scale automatically when the load increases and reduce allocated resources when the load reduces.</p><p>Further, cloud providers also provide significant discounts for sustained use (instance reservations, sustained use discounts, etc.). So how do they manage their excess capacity? Some cloud providers have created marketplaces for their excess capacity known as spot or preemptible instances. These are available at significant discounts but for a limited amount of time. A lot of customer find these useful for applications with dynamic loads.</p><h3>Time to “Go-Live”</h3><p>In today’s dynamic business environment, cost is only one aspect of hardware game. The other crucial aspect is time. In a traditional enterprise IT environment running in a private data center, once a BoM is created and an order is placed, it can take anywhere between 6 weeks to months for the hardware to arrive. Once it does, the data center staff need to rack and cable the hardware (assuming the power and cooling have already been planned for during design). This adds a significant lead time to the process of application going live. If an application is being built in-house, the hardware procurement cycle also has to align with the release plan. If an application is delayed, the hardware sits idle. If hardware procurement is delayed, then there is business impact of the application not going live as expected.</p><p>In the cloud, this problem goes away, as any resources can be provisioned within a matter of minutes. Hardware architecture and sizing can change and evolve to keep pace with the application needs. Applications can be constantly tested and benchmarked against the hardware using DevOps best practices to ensure that the application and hardware are optimized, both before and after Go-Live.</p><h3>Data Center Contract Expiration</h3><p>Not all enterprises manage their own data centers. Some enterprises choose to host and run their workloads in third party colocation data centers (colos) that provide rack space, redundant power supply, cooling, and network connectivity. In such cases, enterprises enter into multi year contracts with the colos that are renewed periodically. Colo costs are a non-trivial part of the overall IT budget for an enterprise.</p><p>Some enterprise start exploring cloud as an alternative to renting colo space. In such cases, the migrations can be aligned with the colo contract expiration. Depending on the hardware footprint and design complexity, enterprises can start planning such migrations from months to a year in advance.</p><h3>Capacity Expansion</h3><p>These days, businesses (especially online businesses) can see a surge in business due to things like viral marketing campaigns. For such businesses running their infrastructure in a data center, the need to expand capacity temporarily during business peaks can make cloud an attractive option for them.</p><p>On the other hand, enterprises running their own data centers may see the need to expand capacity permanently. But instead of building out or renting more data center capacity, the enterprise may choose to move new applications to the cloud, while running the existing applications on-premises till the hardware becomes end-of-life. This is usually part of a larger cloud migration strategy towards a hybrid or a full cloud model.</p><h3>Digital Transformation</h3><p>Many enterprises starting a digital transformation journey, modernizing their legacy applications and deployment processes to take advantages of the more modern technologies such as NoSQL, containers, microservices etc. For such architectures, cloud’s flexibility and scalability often becomes a natural fit. Enterprises usually take one of three paths to cloud in this journey:</p><ul><li>Migrate underlying infrastructure to cloud and then incrementally modernize the application</li><li>Modernize the application on the current infrastructure, prepare the application for the cloud, and then migrate</li><li>Do fresh development directly on the cloud</li></ul><h3>Partner or Compliance Driven Requirements</h3><p>Some enterprises often choose to migrate to cloud if their business partners or customers are leveraging the cloud and expect their partners to also scale up to meet increasing, and sometimes viral growth in customer demand. This can often be the case in retail, finance or logistics industries.</p><p>Contemporary cloud service providers are often referred to as <strong><em>hyperscale</em></strong>. They operate at a bigger scale than most modern enterprises. As they have to support a wide variety of workloads, they implement necessary security controls to conform to multiple security standards (see <a href="https://aws.amazon.com/compliance/pci-data-privacy-protection-hipaa-soc-fedramp-faqs/">AWS Cloud Compliance</a> page). This makes it attractive for enterprises in compliance driven industries to offload part of their infrastructure security to a cloud provider, while focusing on application, data and operational security (see <a href="https://d1.awsstatic.com/whitepapers/compliance/Data_Residency_Whitepaper.pdf">Data Residency with AWS</a> paper). These CSPs also implement security across their infrastructure more cost effectively than enterprises can typically do inhouse.</p><p>CSPs also provide important features like DDoS, WAF etc, as managed services, which makes it very attractive for enterprises, rather than investing in own software and infrastructure.</p><p><em>This blog is part of our ongoing cloud series. To find out how GlobalLogic can help in your cloud migration journey, please reach out to us at </em><a href="/service/mailto:cloud@globallogic.com"><em>cloud@globallogic.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffd647647feb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globallogic-cloud-and-devops-blogs/drivers-for-cloud-migration-ffd647647feb">Drivers for Cloud Migration</a> was originally published in <a href="https://medium.com/globallogic-cloud-and-devops-blogs">GlobalLogic Cloud and DevOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Guide To Building Your Cloud and DevOps Practice]]></title>
            <link>https://medium.com/@tushar.agarwal/a-guide-to-building-your-cloud-and-devops-practice-a4f3cc8aa2fd?source=rss-7ad6274d3c00------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4f3cc8aa2fd</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Tushar Agarwal]]></dc:creator>
            <pubDate>Mon, 12 Sep 2016 00:00:00 GMT</pubDate>
            <atom:updated>2017-08-22T21:31:22.580Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/851/0*_dl1mQ8wLmrmXR45.png" /></figure><h3>Problem Statement</h3><p>Many product companies start out with basic infrastructure with no or minimal DevOps support. As these companies grow, most of them will face typical infrastructure related challenges during early stages. These can be broadly categorized below:</p><ol><li>Performance issues and service degradation</li><li>System downtime</li><li>Infrastructure bloat and cost overruns</li><li>Security breaches</li></ol><p>To help address these problems early on, companies can engage with one of many DevOps partners in the ecosystem, while they look at building DevOps capabilities internally. In this post, I discusses a roadmap to build a full DevOps capability with an automation focused approach to deployment, monitoring, automation and recovery.</p><h3>Approach</h3><h4>Stage 1 — Work with DevOps partners while building out the “Dev” of DevOps capability</h4><ul><li>Cloud architecture (shared responsibility)</li><li>Functional test automation</li><li>Continuous Delivery / Continuous Integration using tools like Jenkins</li><li>Deployment automation using Chef or Puppet</li><li>Cloud Architecture (shared responsibility) — deployment and optimization</li><li>24x7 Monitoring, Incident Management, Escalation, Fixes, Backup and Disaster Recovery design and rehearsals</li><li>Security Audits — VAPT, Penetration Tests</li><li>Infra cost management and optimization</li><li>Load testing</li><li>Find a suitable DevOps partner</li><li>Work with DevOps partner to design and deploy a scalable, reliable architecture</li><li>Train and track development team on test automation</li><li>Hire deployment and test automation guys who are strong in Chef, Jenkins etc.</li><li>Start building knowledge of at least one cloud platform — AWS/Azure.</li><li>Identify and train select members of your team on cloud architectures and best practices.</li></ul><p>At the end of this phase, cloud architecture should exist as a capability with at least a few people within your organization, preferably leads and senior developers.</p><h4>Stage 2 — Internalize and automate common and repeated ops maintenance tasks</h4><ul><li>Cloud Architecture — Design, deployment and optimization</li><li>Deployment and Ops Automation using Chef, Lambda, Cloud APIs</li><li>Build scripts to automate common tasks such as log rotation, backup and restore, snapshots, DR drills</li><li>VAPT, Penetration Tests, Audits, WAF, Load testing</li><li>Continue improving CI/CD and functional test automation</li><li>24x7 Monitoring, Incident Management, Escalation, Fixes, Backup and Disaster Recovery</li><li>Infra cost management and optimization</li><li>Your internal DevOps team starts building reusable scripts in the context of an Ops automation framework</li><li>Security audits</li><li>Backup and DR</li><li>Performance tests</li><li>Continue to train development teams on architecture</li><li>Get key team members certifications on cloud platforms and network design</li></ul><h4>Stage 3 — Build and Integrate tools to automate notification and escalation workflows where manual intervention is required</h4><ul><li>Build scripts to correlate, aggregate and respond to common alerts. Use ops partner’s team as fallback for manual intervention.</li><li>Build scripts to automate instance reservation and cost optimization.</li><li>Use big data and machine learning tools for insights and automation.</li></ul><h4>Stage 4 — Build out a small Ops team for 24x7 Incident Response to act on workflows, escalations and manual fixes</h4><ul><li>Automation for first line Ops management and incident response</li><li>24x7 incident management team for incident management</li></ul><p>At this point, your internal DevOps team owns and supports the application and infrastructure. You work with the DevOps partner on a consultation basis for new initiatives.</p><p>For an in-depth look at the tools and best practices, please look at my previous post <a href="https://medium.com/@tushar.agarwal/an-introduction-to-devops-practices-and-tools-8cf2aea73ec4">here</a>.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/guide-building-your-devops-practice-tushar-agarwal"><em>https://www.linkedin.com</em></a><em> on September 12, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4f3cc8aa2fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>