A campaign will have an increased number of visits to Andean Shop. The computer needs to decide what to run, how to manage and how to expand capacity without losing orders.
Key concepts
One instance It's the compute environment that runs a load. Su image provides the operating system and initial software. Su shape defines resources as a processor, memory and network feature. Flexible shapes allow OCPU and memory to be adjusted into supported combinations. Check architecture, availability and boundaries: an image x86 does not work intersectitiously with an Arm processor.
One VM He uses virtualised hardware. One instance bare metal provides a dedicated physical server. A Dedicated Virtual Machine Host He dedicated a physical host to his client's VMs. They are different options for isolation and monitoring. "nano instance" is not a general instance category OCI on this issue.
The boot volume contains the starter disc. data volumes can be managed separately. One instance configuration keeps reusable parameters to create instances. It isn't a execution copy of the application and does not replace data backup. A instance pool manage a set of instances with a common configuration.
The presentable instances offer lower-cost capacity that can be retrieved by OCI, ending the instance. They cover with jobs that tolerate interruptions, as a lot that keeps advances and can be re-tested. but with the only instance that keeps an indispensable operation. Check the shapes and supported functions: not all options for a regular VM are available. See presentable capacity.
Loan, connect and scale
When creating a VM select compartment, location, image, shape, VCN, subnet, SSH and storage access. Keep the private key under your supervision. OCI receives public key. A SSH connection requires both OS authentication and network connectivity and rules. Membership of Administrators does not replace the Linux user's key.
Cloud Shell offers a terminal environment with tools such as OCI CLI and session authentication. Do not evade IAM or make any private IP available by itself. To get to a private VM you need a built-up access and connectivity method for that network, for example Bastion or an appropriate private connection.
In vertical climbingReforms the capacity of a compatible instance. may require re-initiation. In Horizontal, you change the number of instances. Autoscaling you can title the state or pool with policies based on metric or programming. Define minimum, maximum and waiting times so as to avoid an unstable response to every short beak.
Live Migration moves a compatible VM between physical hosts while continuing to work with a possible short pause. It's not a universal guarantee of zero interruption or procedure to move any burden between regions. Check compatibility and maintenance at migration of agencies.
Containers, Kubernetes and functions
A container pack an application and user dependencies. Shares the kernel of the environment where it runs. does not remove the existence of the operating system. One image from container and an image VM are different artifacts.
| The necessity of the tent | Service to evaluate |
|---|---|
| Application that needs to control your operating system | Compute VM or bare metal as required |
| Run containers without a Kubernetes cluster | Container Instances |
| Orquestar deployments, services and climbing with Kubernetes | Oracle Kubernetes Engine (OKE) |
| Run Fitted logic with an event or call | Oracle Functions |
In OKE, Oracle manages control plane; The responsibilities about nodes and execution depend on selected options. You are still owner Loads, Access and Setup. The pods run containers, deployments expressed wished copies and services offer stable access. OCI Container Registry stores private or public images as set up.
In FunctionsThe equipment unfolds a package code and defines how to invoke it. An object uploading event can activate the processing of an image. "Serverless" means that you do not manage individual servers for that execution; There are still resources, permissions, boundaries, observability and costs. Query OKE y Functions.
Step-by-step example
- The tent starts with two VMs for an existing application. No need to rewrite it to learn OCI.
- Captures launch parameters into an instance configuration and creates a pool.
- place the pool behind a balancing machine. Keep orders out of the ephemeral disc and avoid sessions that depend on a single VM.
- Define an autoscale policy. A didactic example from two instances allows up to four and increases capacity if the metric remains high during the set-up. Those numbers are the case, and they are not required OCI values.
- Also check the decline: before withdrawing capacity, requests and data have to be saved.
For the production of miniatures, the tent evaluates Functions fired by events. It's an independent decision about the main implementation runtime.
Common errors
- "Autoscaling fixes a slow database." Add frontens does not remove the shared bottle neck. Watch the load before climbing.
- "A instance configuration preserves my orders." He describes how to create instances. data require their own strategy.
- "Serverless has no servers and no responsibilities." The supplier removes his or her administration. code, access and operation continue to matter.
Retirement exercise
The tent wants to run a processing container without keeping Kubernetes. A different task should transform every photo at an event. What options would you evaluate? What information would make you reconsider them?
Solution
Container Instances for container without own cluster and Functions for task by event. If the first application requires Kubernetes's APIs and orchestration, consider OKE. If the second requires executions or resources incompatible with Functions's boundaries, another run will be evaluated. The word "container" does not require a choice of Kubernetes.
Sources and review
Query Compute, autoscale, Container Instances y migration. Compare image and shape, vertically and horizontally and OKE and Functions with an own example.