Skip to main content

Dev ops functional spec notes

Dev ops

http://blog.sonatype.com/2009/04/what-is-a-repository/#.UurWWHddUp8

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
http://en.wikipedia.org/wiki/List_of_build_automation_software

--------------------------------------------------------------------------
| 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.
http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr
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.






Comments

Post a Comment

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 @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     pub...
21 comments
Read more

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 ?   GNU GPL v2 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 c onstructor which takes these 3 arguements          // filename is the the file to be validated and here ...
7 comments
Read more

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column ...
11 comments
Read more