vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Architecture framework aspects and domains 

Technology taxonomy of aspects and domains can be applied to develop end-to-end platform or application architectures on any cloud provider. Enterprise Cloud Solutions need to address requirements across the various aspects and domains.

Zoom

![Architecture framework heat map](https://cloud.ibm.com/docs-content/v1/content/c4eda16af9bf94195f92755cfc75c78861e5505c/architecture-framework/images/heatmap.svg)

Figure 1. Architecture framework heat map



 Aspects 

The Aspects are shown in column 1 and cover the different layers of the solution stack, from IT infrastructure through the application, as well as nonfunctional requirements and operational aspects.

The application platform aspect includes some of the application workload types and can be extended to include additional workloads. The Data aspect covers common application data requirements.

Most of the aspects, like Compute, Storage, Networking, Security, and Resiliency are self-explanatory because they describe either the IT environment or common nonfunctional requirements that are table stakes for any enterprise solution.

The DevOps and Service Management cover the operational aspects of the solution.





 Domains 

Domains are the capabilities or functions within an aspect. For example, within the Security aspect, Data Security, Identity and Access Management, and Application Security are examples of functions that are contained in that aspect.

Each domain then contains a set of component options available to meet solution requirements.





 Components 

The component options for each domain are determined by the target cloud deployment model and cloud service provider under consideration.

Components are products or technology choices that satisfy the requirements for a specific category. Components options are determined by the target cloud service provider.





 Example taxomony 

The following are examples of cloud deployments and cloud service providers.

Cloud deployment model
: Public, Private, Hybrid, Multi-Cloud, Distributed Cloud

Cloud platform
: IBM Cloud, AWS, Azure, GCP, other cloud

The following table illustrates component options for the Containers domain across various Public Cloud Service Providers. Note that this is just a sample and not a comprehensive list of available services on each cloud provider.
IBM Cloud Load Balancer,Building infrastructure



* 10 minutes
* 2021-04-20



[Regional snapshots in 3-tier architecture](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-regional-snapshots-3-tier-arch)Regional snapshots in 3-tier architecture

Block storage snapshots can be created in IBM Cloud® VPC Gen2. You can use this feature for a backup and restore of a 3-tier application. Block storage snapshots can also be used to scale out a 3-tier system with minimal changes to your application.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 2021-06-25



[Deploying n-tier application with IBM Cloud single availability zone](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-deploy-n-tier-app-szr)Deploying n-tier application with IBM Cloud single availability zone

This tutorial walks you through setting up a resilient environment for an n-tier application in an IBM Cloud® for a single availability zone. The IBM Cloud VPC infrastructure that is created uses Intel Xeon CPUs and additional Intel technologies. In this tutorial, you create your own VPC, then create subnets in one zone of the region, then you provision the virtual server instances.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 60 minutes
* 2021-12-14



[Deploying server pools and origins in a single region](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-ha-pools-origins)Deploying server pools and origins in a single region

Use this tutorial to deploy availability pools in a VPC for a single MZR. Creating server pools with origins provides your DevOps team with a staging environment so they can validate near-production ready code in parallel with an existing production environment.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+3
Satellite reference architecture use cases 

Use cases for the [Satellite reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-about) for the IBM Cloud for Financial Services typically fall into the four categories in the following table.



Table 1. Overview of use cases for the Satellite reference architecture
The rows are read from left to right. The use case title is in the first column. The second columns describes the use case referenced in the first column.

 Use Case Description 

 Platform modernization Innovate faster and free your team to develop applications with Red Hat OpenShift on IBM Cloud on-premises. Establish container portability and PaaS foundation for developer services and digital supply chain operations. Achieve improved cybersecurity with industry-leading Keep Your Own Key encryption. 
 Concentration risk Mitigate regulatory concerns about concentration risk by using a hybrid cloud deployment model that uses Satellite to extend secure Financial Services Validated offerings from IBM Cloud to your data center. 
 Data residency Manage local data requirements — storage (residency) and legal protections (sovereignty) — by keeping data in-country and accessing public cloud services. Improve data privacy (cybersecurity) for regulated data with industry-leading Keep Your Own Key encryption. 
 AI and automation Gain new insights and process automation by enhancing databases on-premises with IBM Cloud Pak AI and automation services that are deployed with Red Hat OpenShift on IBM Cloud. Maintain control of data on-premises for performance, sovereignty, and regulatory requirements. 



Two uses cases from real financial institutions are presented in the following sections.



 US regional bank 

During a time-sensitive merger, a US regional bank needed to integrate two entities’ IT operations securely and bring consistency across container platforms in on-premises branch locations without adding overhead. Satellite enabled the customer to establish a location that used its existing data center infrastructure and create multiple Red Hat OpenShift on IBM Cloud clusters so that teams could build and host containerized workloads in a consistent way and pay only for what they consumed. This scenario is an example of using Satellite for platform modernization.

The following diagram shows a high-level overview of the architecture that is used by this financial institution.

Zoom

!
Isolated recovery environment solution architecture 

The isolated recovery environment solution architecture uses a VMware vCenter Server® instance with the Veeam® service, gateway cluster, and Juniper® vSRX options. They create an air gapped cyber-recovery environment separate from the production environment. This isolated recovery environment is managed and accessed by using a separate cyber-recovery team. The Veeam service is enhanced with a Veeam Linux® hardened repository for immutable storage.

The solution architecture is suitable for clients who want to move a copy of critical data away from the production environment, backup systems, and personnel to an environment that requires separate security credentials. The solution architecture does not preclude any of the vCenter Server options, such as Caveonix, Entrust, and VMware Aria® Operations™.

Zoom

![Isolated recovery environment solution architecture](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/veeam-cr-sa-ire.svg)

Figure 1. Isolated recovery environment solution architecture

Key elements of the isolated recovery environment solution architecture include:



* Production data that must be recovered if a cyberattack is subject to a cyber-recovery backup to the cyber-recovery site and written to immutable storage in the Linux hardened repository.
* The cyber-recovery site is the IBM Cloud® account, resource group, and data center location where the isolated recovery environment is located. If the production environment is in IBM Cloud, then a different IBM Cloud account is recommended for the cyber-recovery environment to enable segmentation.
* The solution architecture supports only production data that is hosted in a VMware vSphere® environment. It does not support physical servers or other hypervisors.
* The Veeam service in the isolated recovery environment provides a cyber-recovery backup of the specified production virtual machines (VMs). It writes the backup data to the Linux hardened backup repository in the isolated recovery environment.
* Cyber-recovery backup proxies, managed by the Veeam service in the isolated recovery environment, are required to be hosted in the production site.
In this getting started tutorial, you use IBM® Cloud Shell to clone a sample Node.js app. IBM Cloud Shell is a cloud-based shell workspace that you can access through your browser. It's preconfigured with the full IBM Cloud CLI and tons of plug-ins and tools that you can use to manage apps, resources, and infrastructure.

Cloud Shell



* 30 minutes
* 2022-11-09



[Creating a three-tier highly available architecture on an IBM Cloud VPC](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-create-three-tier-architecture)Creating a three-tier highly available architecture on an IBM Cloud VPC

This tutorial describes the three-tiered architecture of an application that is rehosted on IBM cloud. The tutorial outlines the steps to implement a Highly Available solution in the IBM Cloud VPC infrastructure that spans multiple availability zones in one region. The strategies can differ and vary depending upon your application (web, app, and DB) and the redundancy necessary at each level. The tutorial provides a few guidelines for setting up a three tier OLTP application. Wherever possible, guidelines are provided on infrastructure, security, and operations. You might need to refer to your vendors’ supported methods of replication for the tiers, depending on the software components in your architecture.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 60 minutes
* 2021-06-24



[Architecture for a resilient infrastructure for a single availability zone](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ref-arch-saz)Architecture for a resilient infrastructure for a single availability zone

Deploying your application across the availability zone in a multiple-zone region provides the highest resiliency, 4 9's. However, there are scenarios where deploying across the zones is not wanted, such as needing the latency to be minimal or the application is deemed not critical.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2
* [Working with Virtual Machines](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-DF0C111D-B638-4EC3-B805-CC33994F8D53.html)



Check the Terraform registry for more detailed information about the provider, resources and data sources:



* [VMware Cloud Director Provider](https://registry.terraform.io/providers/vmware/vcd/latest/docs)
Structuring your Red Hat OpenShift environment 

Your Red Hat OpenShift on IBM Cloud is linked to one IBM Cloud infrastructure portfolio only. Within your account, you can create clusters that are composed of a master and various worker nodes. IBM manages the master, and you can create a mix of worker pools that pool together individual machines of the same flavor, or memory and CPU specs. Within the cluster, you can further organize resources by using namespaces and labels. Choose the best mix of cluster, flavors, and organization strategies so that you can make sure that your teams and workloads get the resources that they need.



 What type of cluster and flavors should I get? 

Types of clusters: Decide whether you want a [single zone, multizone, or multiple cluster setup](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersha_clusters). Multizone clusters are available in worldwide worldwide IBM Cloud [multizone regions](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-mz). Also keep in mind that worker nodes vary by zone.

Types of worker nodes: In general, your intensive workloads are more suited to run on bare metal physical machines, whereas for cost-effective testing and development work, you might choose virtual machines on shared or dedicated hardware. [Check out the machine isolation and flavors that are available](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesplanning_worker_nodes). For a list of available flavors, see [VPC Gen 2 flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavors) or [Classic flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavors).





 Do I use multiple clusters, or just add more workers to an existing cluster? 

The number of clusters that you create depends on your workload, company policies and regulations, and what you want to do with the computing resources.
Learning about project architecture and workload isolation 

Review the following sample architecture for projects and learn more about different isolation levels so you can choose the solution that best meets the requirements of the workloads that you want to run in the cloud.



 Project architecture 

Projects are an IBM Cloud® platform feature that's supported by a highly available multi-region infrastructure. The project UI and API services are managed microservices, which are deployed to a minimum of three multi-zone regions around the world. A single zone failure results in service instances in other zones that are in the same region taking over. A regional failure results in another region taking over. Project microservices use IBM managed instances of Continuous Delivery Toolchains in at least three regions to run multi-step validation, deployments, and destroy resource jobs.

Projects create instances of IBM Cloud Schematics workspaces in your account and uses them to perform plan, deploy, and destory resource jobs. This ensures that Terraform state storage and any access to private resources is completely under customer control. The Schematics workspace UI, API, and CLI can be used, if needed, to provide additional control and visibility over how Infrastructure as Code (IaC) is managed by projects.

Deleting a Schematics workspace that's used by a project can cause the loss of the Terraform state for that configuration, which can lead to unexpected behavior for project users, for example, causing the project to create duplicate resources on the next deployment. Project-created Schematics workspaces are tagged with the related projects and configurations.





 Project data storage 

Projects are a multi-tenant service that uses a regional data storage model where the data is stored in the region that is selected for the project. Specifically, project configuration data (the deployable architecture reference and selected inputs) is stored in a multi-tenant IBM managed IBM Cloudant database in the project region. The Schematics instances that are created in the customer account for a project are also located in the project region. This ensures that all configuration data is stored in the customer selected region. However, basic project metadata, like the name, description, and state is replicated globally to enable global search and the ability to list all projects across regions.





 Project data protection
The following is a comparison of the IBM Cloud compute service options to help you decide which target compute type is appropriate for your applications. For example, detailed delivery questions, operations, and functional capabilities.



Table 2. Features and functions comparison

 Feature or function IBM Cloud Code Engine IBM Cloud Kubernetes Service Red Hat OpenShift on IBM Cloud 

 Auto-scaling of your application based on load Auto-scaling based on number of HTTP requests is built in. In IBM Cloud Kubernetes Service, applications are synonymous to pods. With Kubernetes, you can automatically [scale up or down your pods based on CPU or memory.](https://cloud.ibm.com/docs/containers?topic=containers-update_appapp_scaling) In Red Hat OpenShift on IBM Cloud, applications are synonymous to pods. With Kubernetes, you can automatically scale up or down your pods based on CPU or memory. [Open Shift has a "Serverless add-on which allows load-based auto-scaling.](https://cloud.ibm.com/docs/openshift?topic=openshift-update_app) 
 "Scale-to-zero" of applications when idle Yes, Scale-to-zero is built in. No, minimum of pod replicas must be <= 1. No, minimum of pod replicas must be <= 1. Open Shift has a "serverless add-on" which allows scale to zero 
 Deployment of specific workload types Almost anything that can be containerized, web apps, event-driven serverless functions, micro-services, batch jobs [Types of typical workloads being moved to IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-strategy) <br>[Use cases](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_intro) <br>Can integrate IBM Cloud Code Engine with IBM Cloud Kubernetes Service.
Design the structure of your environment 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

Instead of the traditional, strictly defined development, test, and production methodology, you can implement an environment where developers and testers can collaborate along with other team members. If you design the way you want to develop and deliver your apps, create spaces to fulfill that methodology. Instead of designing your environment from the organization level down, consider designing your environment from the space level up.

Consider the scale and scope of the apps you plan to develop and deploy. A Cloud Foundry space can be used as a development environment for one or more apps that are tightly connected or defined. Apart from a development space, for example, you can create spaces for unit testing, performance testing, and integration testing. Spaces can also be defined for build, staging, and production. Each of the spaces that you create can be shared with different team members within the same organization.

Create separate Cloud Foundry organizations when you have people working on different business areas and where their activities do not overlap. If there are two independent groups, then creating an organization for each defines clear boundaries for the delivery and management of team players and resources. You can define an API to communicate between the organizations.

Cloud Foundry organizations can be created to match how you want to work rather than the structure within a company. Typically, company organizations can change but the development and maintenance of an app continues regardless. Design your instance for the lifetime of the apps and not on your company organization structure.

Iterative development and deployment can result in apps that expand quickly. Your delivery process design must be able to scale up quickly and easily. You want continuous development with a fast deployment rate. Having your development and production spaces in the same organization provides access to the same resources. Managing different spaces within a single organization reduces the administration workload. The development, test, and operations personnel can collaborate easily if they are working within the same organization.

Implement a naming standard to clearly identify the organization and space usage.
* Enterprise Hybrid Cloud deployment: run workloads on IBM Power in both Cloud IaaS and on-premises, accessing Cloud's self-service, fast delivery, elasticity, and connectivity to other IBM Cloud® services. Although your Linux® workloads are running in IBM Power Systems Virtual Servers, you keep the same scalable, resilient, production-ready features that Power Systems hardware is known to provide.
* Infrastructure customization: Flexibility of IBM Power Systems Virtual Servers hardware capabilities:



* Cores (CPU)
* Memory (RAM)
* Data volume size
* Data volume type / performance tier
* Network interfaces
* PowerVM Host Pinning Policy (soft or hard)
* PowerVM Host CPU Binding (dedicated or shared)





For more explanation information about IBM Power Systems Virtual Servers, see [IBM Power Systems Virtual Servers](https://www.ibm.com/cloud/power-virtual-server) on ibm.com and [IBM Power Systems Virtual Servers](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-about-virtual-server) on IBM Cloud Docs.

If you'd like to compare your current environment's performance to what's available through the IBM Power Systems Virtual Server service, see the [IBM Power Systems performance report](https://www.ibm.com/downloads/cas/K90RQOW8). For a more condensed comparison, see [IBM Power Systems CPW performance data comparison](https://www.itechsol.com/wp-content/uploads/2018/07/IBM-Power-Systems-CPW-Performance-Data-Comparison-P7-vs-P8-vs-P9-rev3-July-2018.pdf).



 Constructs for provisioning IBM Power Virtual Servers 

As the IBM Power Virtual Server is a complementary offering from IBM Power Systems, it is accessed as an additional offering from the IBM Cloud catalog. To begin using IBM Power Virtual Servers, an instantiation of an IBM Power Virtual Server resource group must first be made.

The below sections explain this in more detail.



 Resource versus Resource Group
See also [host](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2002243).







 client secret 

A piece of information that is used with an application key to verify the identity of an application. An API can be configured to require that client applications supply their application secret with their application key. The application secret functions effectively as a password known only to the application. The application secret is passed by the client using an HTTP query parameter.





 cloud computing 

A computing platform where users can have access to applications or computing resources, as services, from anywhere through their connected devices. A simplified user interface or application programming interface (API), or both, makes the infrastructure supporting such services transparent to users.





 cloud portability 

The ability to move applications and services across public or private cloud computing environments, or from different cloud providers.





 cloud provider 

An organization that provides cloud computing resources.





 cloud resource name (CRN) 

A globally unique identifier for a specific cloud resource. The value is segmented hierarchically by version, instance, type, location, and scope, separated by colons.





 command-line interface (CLI) 

A computer interface in which the input and output are text based.





 community 

A collection of consumer organizations. It is used as a grouping construct when publishing APIs. Communities are used to restrict the visibility and accessibility of APIs.





 component 

In source control management, a grouping of related artifacts in a stream or repository workspace. A component can contain any number of folders and files.





 compute 

Infrastructure or resources that serve as the basis for building apps in the cloud.





 config rule 

See [configuration rule](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3084914).





 configuration rule (config rule) 

A JSON document that defines the configuration of resources and validates the compliance based on security requirements when a resource is created or modified.





 confusion matrix 

A table that provides a detailed numeric breakdown of annotated document sets.