4.6
Canary Release
“This is an approach to software deployment that leverages the "canary in the coal mine" metaphor. In essence, a release into production is delivered to successively larger end-user populations to test the correctness (either in functionality or performance) of the latest build. The goal is to identify a problem as early as possible, and impact the fewest number of customers. In addition, this practice potentially enables an easier recovery, should the need occur.”30
The following is an example of this design:
Figure : Canary Deployment from http://martinfowler.com/bliki/CanaryRelease.html
ChatOps
“It is the pattern of automating operations tasks with an automated chat robot, or "bot," from within a chat room.4 Specifically, DevOps team members issue commands to perform code deployments, for example, via Internet Relay Chat (IRC) to a chat bot, which then executes them through scripts, etc. This enables the entire team to have real-time collaboration, and ensures that everyone is aware of the current status of an operation in progress.31”
Containers
Gartner defines Containers the following way:
“The concept of the container is simple: Similar to how a VM virtualizes hardware for multiple OSs, a container virtualizes a single OS for multiple applications (also called ‘shared-OS virtualization’). Put simply, a container is effective at OS process isolation.32”
Its further states:
“Containers are ideal tools for those applications that require agile development and change, horizontal composability (with loosely coupled microservices), and horizontal scalability. Containers are also much more accessible and easy to use by developers than VMs, and they enable better collaboration and sharing of lightweight microservices.
Container implementations vary, but, in general, a container has its own unshared user space and unique files. A container also shares an OS kernel, libraries and files with other containers on the OS. While containers are theoretically portable, they must be redeployed on an OS with the same base capabilities and may have dependencies on specific storage, networking or security architectures. In practice, this limits portability significantly.33”
Microservices
James Lewis and Martin Fowler define the microservices style in this way:
“In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.34”
Principal of Least Privilege
“Every program and every user of the system should operate using the least set of privileges necessary to complete the job”.35
ServiceNow
Information Technology Service Management Software as a Service Provider. http://www.service-now.com.
6LIST OF ACRONYMS
Acronym
|
Description
|
AHC
|
Anywhere Healthcare
|
AMQP
|
Advanced Message Queuing Protocol
|
CCCP
|
Connected Cardiac Care Program
|
CPOE
|
Computerized Patient Order Entry system
|
DICOM
|
Digital Imaging and Communications in Medicine
|
EIP
|
Enterprise Integration Patterns
|
EMR
|
Electronic Medical Records System
|
ER
|
Entity and Relationship diagram
|
ESB
|
Enterprise Service Bus
|
GlocoHCP
|
Gloco Healthcare Providers Inc.
|
HL-7
|
Health Level-7
|
JVM
|
Java Virtual Machine
|
LIS
|
Laboratory Information System
|
MIP
|
Medicare Incentive Program
|
PABS
|
Patient Admission and Billing System
|
PACS
|
Picture Archiving and Communication System
|
RIS
|
Radiology Information System
|
SNOMED-CT
|
Systematized Nomenclature of Medicine - Clinical Terms
|
SOA
|
Service Oriented Architecture
|
TIP
|
Team IT Partners
|
UIUX
|
User Interface and Experience
|
VPC
|
Virtual Private Computing
|
VXLAN
|
Virtual Extensible LAN
|
Share with your friends: |