Continuous Delivery

-
Getting software released to users is often a painful, risky, and time-consuming process.
Continuous Delivery can help large organizations become as lean, agile and innovative as start ups. Through reliable, low risk releases, Continuous Delivery makes it possible to continuously adapt software in line with user feedback, shifts in the market and changes to business strategy. We speed up the whole process while improving quality. Test, support, development and operations work with each other as one delivery team.


From Continuous Integration to Continuous Delivery

Continuous Integration is best described in a landmark article by Martin Fowler. Originally one of the fundamental practices outlined in the Extreme Programming (XP) methodology, Continuous Integration (CI) has become an essential ingredient for teams doing iterative and incremental software delivery.
The term Continuous Deployment was coined around the same time to describe how similar automation techniques could be applied to the actual release of software from one environment into another. Essentially, organizations who practice Continuous Deployment are said to be always 'ready to release'.

"Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly." 
- Martin Fowler, ThoughtWorks Chief Scientist

Comments

Post a Comment

Popular posts from this blog

PostgreSQL bytea and oid

-
I came across with following issue when i'm trying to save the uploaded file in to the database as a byte array using hibernate, JPA 2.0  annotation with Postgre SQL. even though in this stage i'm pretty much new to Postgre SQL, It has two type of data types to represent the binary data or BLOB, since i'm using hibernate jpa annotations use the annotation @Lob to indicate the byte[] of data to persist as a binary data. @Lob   @Basic(fetch = FetchType.LAZY)  public byte[] getPicture() { return picture;  }    exception : java.sql.SQLException: ERROR: column "picture" is of type bytea but expression is of type oid   Then i understood the issue with the data types.but when the hibernate generating the table it creates the  column with data type "oid" , after removing this annotation it creates a table column with "bytea" data type. and i'm in doubt which would be the most suitable data type to use.   Then i found the difference be
Read more

Adding MySQL datasource to JBOSS AS 7

-
Retrieve the MySQL Connector The connector can be downloaded from:  http://dev.mysql.com/downloads/connector/j/ . The current version at the time of writing is 5.1.24, further sections of this guide assume that version number. Unzip the connector to your downloads folder and save the location of the main JAR in a variable which we can refer to later: Add a Module to AS 7 AS 7 uses a module system to provide isolation in class loading. We need to create a new module which contains the MySQL Connector J JAR. Move to the the AS installation directory and create the folder structure for the new module: export JBOSS_HOME =~ / Development / jboss-as-web-7.0.0.Final cd $JBOSS_HOME mkdir -p modules / com / mysql / main Copy the driver jar to the new directory and move to that directory: cp MYSQL_JAR $JBOSS_HOME / modules / com / mysql / main cd $JBOSS_HOME / modules / com / mysql / main Define the module in XML. This is the key part of the process.  v
Read more

Microservices Architecture with Spring Boot in 15mins

-
Image
1. Introduction Microservices is not a new term. It coined in 2005 by Dr Peter Rodgers then called micro web services based on SOAP. It became more popular since 2010. Micoservices allows us to break our large system into number of independent collaborating processes. Lets see below microservices architecture. 1.1 What is Microservices Architecture? Microservices architecture allows to avoid monolith application for large system. It provide loose coupling between collaborating processes which running independently in different environments with tight cohesion. So lets discuss it by an example as below. For example imagine an online shop with separate microservices for user-accounts, product-catalog order-processing and shopping carts. So these components are inevitably important for such a large online shopping portal. For online shopping system we could use following architectures. 1.2 Shopping system without Microservices (Monolith architecture) In this architecture we are
Read more