Some common terms and definition

IT is full of buzzwords …

SRE – Site Reliability Engineering

Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies that to IT operations problems. The main goals are to create ultra-scalable and highly reliable software systems.

A site reliability engineer (SRE) will spend up to 50% of their time doing “ops” related work and spend the other 50% of their time on development

DevOps

DevOps (development and operations) is a software development phrase used to describe a type of agile relationship between Development and IT Operations. The main characteristic of the DevOps movement is to strongly advocate automation and monitoring at all steps of software construction, from integration, testing, releasing to deployment and infrastructure management.

DevOps isn’t a job description/title, is a methodology.

Provisioning

Provisioning is the process of preparing new systems for users. The systems are generally virtualized and instantiated on demand. Configuration of the machines to install operating systems, middleware etc. is handled by automated system configuration management tools, which also verify that the desired configuration is maintained.

Canary Release

A go-live strategy in which a new application version is released to a small subset of production servers and heavily monitored to determine whether it behaves as expected. If everything seems stable, the new version is rolled out to the entire production environment.

Configuration Management

A term for establishing and maintaining consistent settings and functional attributes for a system. It includes tools for system administration tasks such as IT infrastructure automation. (ansible/salt)

Orchestrator

A tool to provision, deploy, manage network, check security groups, create VM’s that in some cases can do the whole in an automated way based on defined conditions. (saltstack)

IaC – Infrastructure as code

The process of managing and provisioning computer data centers through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. (terraform)

OSI model (Open Systems Interconnection)

 7. Application   --- (your app)
 6. Presentation
 5. Session
 4. Transport     --- (TCP/UDP)
 3. Network
 2. Data link
 1. Physical layer

https://nbari.com/post/osi/