Next, we define and examine three common deployment scenarios, highlighting which adoption model is used for each subsystem: Through the rest of this paper, we go to great lengths to identify key capabilities, features, or attributes that help customers decide which adoption model to use for which subsystem and when. In these instances, we recommend working with your Citrix partner/sales/engineering team to help overcome them. In other cases, non-technical items (politics, budgetary/contractual considerations, cloud readiness deficiencies, regulatory/compliance considerations, and such) may discourage the usage of cloud services. Sometimes, use case requirements (with technical attributes or shortcomings in a currently available/specific cloud service) need adopting a combination of cloud services and a customer managed component: we focus on these in this paper. We don’t offer this stand blindly - while we do believe cloud services, in the end, offer overwhelmingly positive benefits for our customers, we recognize that not all organizations/deployments are able to use cloud services for all subsystems today. We take a stand for cloud services, recommending that most organizations use or plan to use cloud services where feasible. We then break the components of a Citrix virtualization system down into multiple subsystems, and categorize them by adoption model: Adoption Model / Subsystem functionĬustomer Managed (installed from downloaded binaries)Ĭloud Service (delivered via Citrix Cloud)Ĭitrix Workspace (the service, consumed via Citrix Workspace app or web browser)Ĭitrix StoreFront (plus Citrix ADC/Gateway for most use cases)Ĭitrix Workspace (plus Citrix ADC/Gateway for certain use cases) We start by defining two primary technology adoption models:Ĭustomer Managed and Cloud Services. To help customers and partners understand these decision points, we have introduced and defined some specific terminology to set the appropriate context, then used this context to highlight the critical decisions and implications to consider as you plan your deployment. This paper is written for the Citrix customer or partner who’s considering or planning to deploy these technologies on AWS’ public cloud infrastructure.įor both existing customers looking to modernize their infrastructure and new customers looking to deploy Citrix virtualization and networking technologies, there are several key high and low level decisions which must be made along the way to help facilitate a successful deployment. This flexibility allows Citrix technologies to serve various different use cases, business types, integration requirements, and operational models. There are many ways in which these technologies can be licensed, deployed, integrated, and managed. Overview and Executive SummaryĬitrix virtualization and networking technologies have been successfully serving the needs of enterprises large and small for nearly three decades. In this document, we use the Citrix Architectural Design Framework to organize and present the leading practices, recommendations, and design patterns which are used by Citrix and select Citrix consulting partners. It is not meant to be a “How-To” reference - Citrix considers those Deployment Guides, and they are now delivered and maintained separately from Reference Architectures. This document is intended to help Citrix partners and customers understand the most critical design decisions necessary to successfully deploy Citrix virtualization technologies on Amazon’s public cloud. Questo articolo è stato tradotto automaticamente. (Aviso legal)Įste artigo foi traduzido automaticamente. (Clause de non responsabilité)Įste artículo ha sido traducido automáticamente. (Haftungsausschluss)Ĭe article a été traduit automatiquement. This article has been machine translated.ĭieser Artikel wurde maschinell übersetzt. Questo contenuto è stato tradotto dinamicamente con traduzione automatica. (Aviso legal)Įste texto foi traduzido automaticamente. (Clause de non responsabilité)Įste artículo lo ha traducido una máquina de forma dinámica. (Haftungsausschluss)Ĭet article a été traduit automatiquement de manière dynamique. This content has been machine translated dynamically.ĭieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |