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

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <
3 comments
Read more

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;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co
21 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     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc
11 comments
Read more