OCI Infrastructure Automation with Terraform & Azure DevOps

Serverless computing runs your code only while an event is calling it: the provider conjures an execution environment on demand, throws it away afterwards, and charges for work performed instead of for capacity sitting idle.

A container is an application packaged together with the libraries and configuration it needs, run as an isolated process on a host that is already switched on, so the same package behaves the same way on a laptop, in a build pipeline and in production.

Object storage keeps every file as a self-contained object (the bytes, a unique key and some metadata) inside a flat bucket you read and write over HTTP, with no drive to mount and no directory tree underneath it.

Caching keeps the result of expensive work, such as a rendered page or a database query, and serves that stored copy until it expires, making it the largest single source of speed on any busy website.

Uptime is the proportion of time a service answers requests, quoted in nines, and a service level agreement is the contract clause setting out how that proportion is counted and what the provider owes when it falls short.

Shared hosting puts your website on a machine that is simultaneously running hundreds of other people's, pooling its processor, memory and disk between all of you, which is both why it costs so little and why your speed partly depends on strangers.