Dhananjayan Govindan dhana-git

Puppet - Infrastructure as Code : Quick start (IEP-AED)

A set of guidelines that helps us to avoid having a bad design.

The structure of software components, their inter-relationships, and the principles and guidlines governing their design and evolution over time.

The combination of distinctive features in which an architecture is performed or expressed.

A Web application architecture

REST-The server application adheres to REST principles, i.e. it exposes a set of resources that are meaningful to a user sitting in front of a browser, each resource has its own URI, all of the information necessary for handling a request is contained within the request itself, HTTP methods are used in line with their definition, and the resource state is maintained by the server (stateless communication).
APPLICATION-LOGIC - All application logic resides on the server.
HTTP - The client interacts with the server through RESTful HTTP requests.
LINK - A user must be able to link to a specific piece of information, e.g. by copying the address from the browser's address bar and pasting it into an e-mail, creating a bookmark, or using any of the fancier ways to share URIs.
NON-BROWSER - It must be possible to use the server's logic through user agents other than a browser, e.g. a command-line client s

The Self-contained System (SCS) approach is an architecture that focuses on a separation of the functionality (domain) into many independent systems, making the complete logical system a collaboration of many smaller software systems.
This avoids the problem of large monoliths that grow constantly and eventually become unmaintainable.
The idea is to break a large system apart into several smaller self-contained systems, or SCSs, that follow certain rules.

A microservice is probably smaller than an SCS. Of course it is possible to split an SCS even further so it consists of microservices. There are usually fewer SCSs than microservices.
SCSs should ideally not communicate with each other while this is fine for microservices.
SCSs should favor integration at the UI layer. Microservices typically focus on integration at the logic layer.
SCSs have a UI, while microservices might separate the UI from the logic in its own service.

	<?xml version="1.0" encoding="UTF-8"?>
	<project>
	<actions/>
	<description>FIS on OpenShift using S2I strategy</description>
	<keepDependencies>false</keepDependencies>
	<properties/>
	<scm class="hudson.scm.NullSCM"/>
	<canRoam>true</canRoam>
	<disabled>false</disabled>
	<blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>