Module 1 Flashcards
What is cloud native?
Cloud-native is an approach to achieving goals that benefit everyone involved in developing, running, and managing
an application in the cloud.
Goals of cloud-native
The goals of cloud-native are to adopt design patterns, paradigms, and techniques that enable loosely coupled
systems built around Microservice Architecture principals.
Service meshes
are configurable infrastructure layers that describe how various services that comprise
an application communicate with each other.
API Gateway technologies
s help formalize, configure, and secure the service endpoints into an
application.
What is CI/CD?
It describes automation that emphasizes tooling around the code, build and deploy phases of
the software-development lifecycle.
What is devsecops?
DevOps but with an additional focus on security and compliance.
DevSecOps builds on the cultural changes of DevOps to integrate the work of security teams sooner
rather than later.
Cloud-native design
- Automated using Agile processes.
- Easily operable or manageable across multiple cloud environments.
- Observable at all application development lifecycle stages.
- Resilient to failures in production.
Immutable infrastructure - i
- is a paradigm in which application images are never modified after they’re
Web scale
is the seamless scaling of applications across cloud boundaries to meet consumer demands.
Continuous integration
– describes the automated processes used to build, test, and merge application
code changes using source code control systems with integrated change management.
Continuous delivery
describes the automated processes used to package and release application code.
Continuous deployment
describes the automated processes used to deploy and orchestrate
applications to target cloud environments.
Infrastructure-as-code (IaC)
are scripts and declarative configurations that describe the infrastructure
resources the application needs including servers, operating systems, storage, and network
Test-Driven Development (TDD)
is when functional and unit tests are written first for a new feature or
change and then the actual code is written to pass it.
Pair programming
– is when two developers work together and take turns where one developer writes
the code and the other one observes and warns of potential bugs or errors