Skip to main content

Dev ops functional spec notes

Dev ops

Repository - a collection of binary software artifacts & metadata stored in a defined directory structure.
e.g - maven, ivy, mercury,
Maven - can store jar, ware, zip etc

Release Artifact  - never change, static artifacts created by specific versioned release.
Snapshot Artifact - generated during development, has both version and timestamp in its name.

Coordinates - for locating artifcats. e.g. maven (groupId, artifactId, version, packaging). Coordinates are translated into url.

List of build automation softwares

| Source Control   |   Build Tools   | Continous Integration |
| SVN               |   Ant                   | Jenkins/Hudson           |
| Mercury          |   Maven              | AnthillPro                   |
| Perforce          |   Gradle              | Bamboo                      |
| Git                  |                            | Cruise Control            |
| CVS               |                            | BuildWeb                   |

John Allspaw and Paul Hammond of Flickr Presentation on Dev Ops.
Key points.
Traditional thinking - Dev - adds feature, Ops - keep site stable and fast
Argues - Ops job is to enable the business NOT to keep the site stable and fast, and this is Dev job too.
Business requires change! But change is the root cause of outages!
Choice - discourage change to keep business running or allow?
Lower risk with tools & culture.
Tools - Automated infrastructure (chep, puppet, AppD etc). One step built and deploy
Culture - Respect, Don't hide things, Trust, Healthy attitude towards failure, Avoid blame.


Popular posts from this blog

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax.

Example 1: Stores list of Strings in an Entity

public class Users implements Serializable {

    private static final long serialVersionUID = 1L;
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Long id;
    private List<String> certifications = new ArrayList<String>();

    public Long getId() {
        return id;

    public void setId(Long id) { = id;

    public List<String> getCertifications() {
        return certifications;

    public void setCertifications(List<String> certifications) {
        this.certifications = certifications;

        Users u = new Users();
        u.getCertifications().add("Sun Certified Java Programmer");

Generated Tables

Column --> ID
    Row             1


Validating CSV Files

What is CsvValidator ?
  A Java framework which validates any CSV files something similar to XML validation using XSD.

Why should I use this ?
  You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference.

Why did I write this ?
  Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing.

What is the license clause ?

Are there any JUnit test cases for me checkout ?
 Yes, source

How to integrate in my existing project ?

Just add the Jar which can be downloaded from here CsvValidator.jar and you are good.

Instantiate CsvValidator constructor which takes these 3 arguements

         // filename is the the file to be validated and here is a sample         // list - defines all the fields in the above csv file ( a field has index, type, isOptional, rege…

ArrayList vs LinkedList vs HashSet Performance Comparision

ConclusionsInserting & Reading sequentially from Collection prefer LinkedList/ArrayListInserting & Reading/Deleting by Search/equals from Collection prefer HashSetInserting, ArrayList & LinkedList performs best while HashSet takes double the timeReading, HashSet performs best while ArrayList & LinkedList are marginally lessDeleting, HashSet performs 10 times better than ArrayList & ArrayList performs 4 times better than LinkedList. LinkedList is slow because of sequencial search Bottom line : unless you are not going to iterate using for(Integer i : list ) then prefer HashSet
Inserting/Reading/Deleting integer's from zero till countJDK7Collectionactioncounttime msArrayListInsert1000/1LinkedListInsert1000/1HashSetInsert1000/1ArrayListInsert100005LinkedListInsert100004HashSetInsert100007ArrayListInsert10000011LinkedListInsert10000011HashSetInsert10000021ArrayListGet/Read1000LinkedListGet/Read1000HashSetGet/Read1000ArrayListGet/Read100004LinkedListGet/Read100003Has…