AWS Lambda – Function Focus and the Future

This post was written by Rich Bosomworth.

The term serverless refers to a model of cloud compute that runs code in response to events. AWS Lambda is currently the more popular choice of serverless technology against competing offerings such as IBM OpenWhisk or Azure Functions.Continue reading “AWS Lambda – Function Focus and the Future”

Addressing Build & Deploy Anti-patterns for Continuous Delivery Success

fiercely-1

What follows is a guest post from Fiercely, a software consultancy based in Coimbra, Portugal.

After a great presentation at IPEXPO Europe on “Continuous Delivery Anti-patterns from the wild” by Matthew Skelton, we quickly drew parallels with our own work and experiences here at Fiercely.Continue reading “Addressing Build & Deploy Anti-patterns for Continuous Delivery Success”

Free eBook – DevOps Journeys

devops-cover

DevOps has become a highly common term with more and more organisations adopting it, however, the idea is still quite new and everybody has their own opinion on what it actually is.

Considering this, Linux Recruit interviewed fourteen industry experts about their experiences and tried to reach a common definition, overviewing the current state of DevOps and what the future holds.

We are featured in the report as well, you can see if your thoughts match ours if you click the link below!Continue reading “Free eBook – DevOps Journeys”

Database Deployability – #5 Source Business Intelligence from a Data Warehouse

This post was written by Matthew Skelton co-author of Team Guide to Software Operability.

Deployability is now a first-class concern for databases, and there are several technical choices (conscious and accidental) which band together to block the deployability of databases. Can we improve database deployability and enable true Continuous Delivery for our software systems? Of course we can, but first we have to see the problems. 

Until recently, the way in which software components (including databases) were deployed was not a primary consideration for most teams, but the rise of automated, programmable infrastructure, and powerful practices such as Continuous Delivery, has changed that. The ability to deploy rapidly, reliably, regularly, and repeatedly is now crucial for every aspect of our software.

This is part 5 of a 7-part series on removing blockers to Database Lifecycle Management that was initially published as an article on Simple Talk (and appearing here with permission):Continue reading “Database Deployability – #5 Source Business Intelligence from a Data Warehouse”

Study methods and exam technique for AWS Solutions Architect Certification (Associate)

This post was written by Rich Bosomworth.

AWS Certification provides many benefits. It deepens product knowledge, provides professional validation and is an enabler for companies wishing to achieve AWS Consulting Partner status as a guarantee of competency to enhance client engagements.

Background preparation for AWS Solutions Architect course

Continue reading “Study methods and exam technique for AWS Solutions Architect Certification (Associate)”

Operability.io 2016 – Automation, monitoring and communication (Day 2)

This post was written by Jovile Bartkeviciute.

Key points from Operability.io Day 2:

OPERABILITY AND EVOLVABILITY – Rebecca Parsons

img_2939

  • Definition of done – you cannot be 75% done, done is done.
  • Evolutionary architecture supports incremental and guided change across multiple architectural dimensions.
  • You want deployments to be boring – you cannot experiment with this.
  • It is irresponsible to use microservises architecture if you do not have mature organisation, devops culture and continuous delivery. Regardless of the benefits, without the high level of communication, microservices puts too much weight on the operations department.
  • Continuous delivery is all about making deployment repeatable.
  • With the central role the technology is playing in our businesses – the operations are treated seriously in they way they weren’t previously.
  • “Devops, Continuous Delivery and Evolutionary Architecture are a locked set.”

Continue reading “Operability.io 2016 – Automation, monitoring and communication (Day 2)”

Operability.io 2016 – Operations is crucial (Day 1)

This post was written by Jovile Bartkeviciute.

4NujEVTr.jpg

After the success last year, the Operability.io returned to London on Monday 19th September. The two-day conference was single line, same as last year, and the speakers were hand-picked and carefully chosen by the organisers. Day 1 started with an opening speech by Marco Abis, with Mark Burgess delivering the first talk.Continue reading “Operability.io 2016 – Operations is crucial (Day 1)”

Database Deployability – #4 Name Things Transparently

This post was written by Matthew Skelton co-author of Team Guide to Software Operability.

Deployability is now a first-class concern for databases, and there are several technical choices (conscious and accidental) which band together to block the deployability of databases. Can we improve database deployability and enable true Continuous Delivery for our software systems? Of course we can, but first we have to see the problems.

Until recently, the way in which software components (including databases) were deployed was not a primary consideration for most teams, but the rise of automated, programmable infrastructure, and powerful practices such as Continuous Delivery, has changed that. The ability to deploy rapidly, reliably, regularly, and repeatedly is now crucial for every aspect of our software.

This is part 4 of a 7-part series on removing blockers to Database Lifecycle Management that was initially published as an article on Simple Talk (and appearing here with permission):Continue reading “Database Deployability – #4 Name Things Transparently”

Database Deployability – #3 Archive, Distinguish, and Split Data

This post was written by Matthew Skelton co-author of Team Guide to Software Operability.

Deployability is now a first-class concern for databases, and there are several technical choices (conscious and accidental) which band together to block the deployability of databases. Can we improve database deployability and enable true Continuous Delivery for our software systems? Of course we can, but first we have to see the problems.

Until recently, the way in which software components (including databases) were deployed was not a primary consideration for most teams, but the rise of automated, programmable infrastructure, and powerful practices such as Continuous Delivery, has changed that. The ability to deploy rapidly, reliably, regularly, and repeatedly is now crucial for every aspect of our software.

This is part 3 of a 7-part series on removing blockers to Database Lifecycle Management that was initially published as an article on Simple Talk (and appearing here with permission):Continue reading “Database Deployability – #3 Archive, Distinguish, and Split Data”

Anti Pigeon Holing or Why Leaders Should Consider Capabilities, Not Job Titles

Credit

This post was written by John Clapham.

Often during a DevOps or agile transformation, we demonstrate the potential of fresh ways of working with a single, pioneering team. Generally these teams produce solid results and there is a strong desire to scale the approach to more teams. This moment is something of a tipping point for the department, successful scaling leads to successful teams, leading to successful projects. How people are picked for those teams is crucial. A team’s make up is just as important as the practices it adopts; personalities, skills, experience and enthusiasm will all determine the drive, output and diligence of the team.Continue reading “Anti Pigeon Holing or Why Leaders Should Consider Capabilities, Not Job Titles”