Term
|
Definition
-Plan for change, implement automatically
-Automate course of action when known problem occurs
-Continuous Monitoring with automated response
-Cloud technology allows for constant change
--Validate configs
--Perform automated checks |
|
|
Term
|
Definition
-basic structure of an application instance
-blue print of online services
-Define web server, php versions, SSL certs, Firewall rules, brute force monitoring |
|
|
Term
|
Definition
-Application instances are constantly built and torn down
-Snapshots revert to known state
-Rollback to known config
-Live boot media, system comes up, is used and is gone, nothing saved |
|
|
Term
|
Definition
-Scale up: Provide resources when demand requires it
-Scale down: when usage is low |
|
|
Term
|
Definition
-New Servers deployed quickly as needed
-Automated deployment and movement of virtual hosts
-Servers added and or moved to other data centers |
|
|
Term
|
Definition
-Takes time to build
-Allows new servers to be created quickly
-Perfect deployment built specifically for an application instance.
-Built from application instance template |
|
|
Term
|
Definition
-Servers located in different areas
-Applications, data, and other critical assets are all separated from each other
-Difficult to find and target systems |
|
|
Term
|
Definition
-High Availability / Uptime
-Guard against hardware failure, servers
-Services always available
-High Network Performance |
|
|
Term
|
Definition
-Redundant hardware components
-UPS
-Redundant Array of Independent Disks
-Back up server or hardware may need to be turned on or configured |
|
|
Term
|
Definition
-Redundant Systems are always on
-Always Available
-Load Balancer
-Redundant components work without intervention or requiring configuration or being powered on |
|
|
