Velocity

Move at high velocity so your team can innovate faster. adapt to changing markets more effectively. Drive business outcomes faster than the competition. The DevOps model enables your developers and operations teams to achieve these results. Increase the frequency and pace of releases so your teams can innovate and improve your products faster. The quicker you can release new features and fix bugs, the faster you can respond to your customers’ needs. Enable the automation of software release process, from build to deployment through continuous integration and continuous delivery.

Reliability

Ensure the quality of application updates and infrastructure changes. Reliably deliver at rapid pace while maintaining a positive experience for end users. Leverage continuous integration and continuous delivery, automating the testing of each change for functionality and resilience. Evolve your monitoring and logging practices for real-time performance management.

Scale

Operate and manage your infrastructure and development processes at scale. Automation and consistency help you manage complex or changing systems efficiently and with reduced risk. For example, infrastructure as code helps you manage your development, testing, and production environments in a repeatable and more efficient manner.

True ownership and collaboration

Build more effective teams under a DevOps cultural model, which emphasises values such as ownership and accountability. Developers and operations teams collaborate closely, share many responsibilities, and combine their workflows. This reduces inefficiencies and saves time while also increasing the quality of code written as support is provided by those writing the code.

Security

The DevSecOps movement ensures security is an enabler in the organisation. Compliance and security requirements are now guided in parallel with project teams.Move quickly while retaining control and preserving compliance. Ensure secure code practices as products are being built. A DevOps model can be adopted without sacrificing security by using automated compliance policies, fine-grained controls, and configuration management techniques. For example, using infrastructure as code and policy as code, you can define and then track compliance at scale.

Interactions over process

We believe in interactions and individuals over strict processes and tools. Discussions, workshops and collaboration always triumph over static spreadsheets and rigid consulting processes.

Outcomes over static documentation

We believe in automation in everything we do. Our infrastructure as code and product code power living and breathing production environments. Static documentation processes will no longer support modern requirements on IT.

Customer collaboration over contract negotiation

We believe in collaborating with our customers to achieve their ever-evolving goals. Every scope change should no longer be negative contract re-negotiations, but rather a rapid step forward as new requirements arrive.

Breaking down the silos.

We believe that if you write something, you need to run it. Writing code with an appreciation for the ease of its continuous running uplifts the overall quality of code. We believe that everyone that is part of a project should be included throughout the process.  The right outcomes are achieved through collaboration from the outset

Experimentation and iteration over Ivory towers

We believe in the concept of experimentation, iteration and feedback loops to achieve a minimum viable product that iterates over time. Gone are the days of “Ivory Tower” architecture, where design is rigidly locked in many months before build begins.

Automation & Infrastructure as Code

Infrastructure as code is a practice in which infrastructure is provisioned and managed using code and software development techniques, such as version control and continuous integration. Through the use of cloud powered APIs, infrastructure can be deployed through code programmatically, with entire environments provisioned through a single command.

Because they are defined by code, infrastructure and servers can be automated to scale up and down consistently, and quickly be deployed using standardised patterns, updated with the latest patches and versions, or duplicated in repeatable ways.

What is an API

An API is a series of functions that enables communication between two or more separate pieces of software. APIs act as a layer over the top of existing applications within your organisation to provide an interface for these once siloed applications with the ability to communicate and share data in ways never available before. This leads to modern customer interactions and experiences including Chatbots, Mobile Apps and Alexa powered voice-enabled services.

What is a Microservice

A microservice is a design approach to building a single application as a set of small services. Each service runs in it’s own process and communicates with other services through a well-defined interface using a lightweight mechanism, such as an API. Microservices are built around business capabilities; each service is scoped to a single purpose. DevOps engineers can use different frameworks or programming languages to write microservices and deploy them independently, as a single service, or as a group of services.

What is Serverless

Serverless technology provides developers with the ability to run blocks of code that perform a function or serve an API (such as performing a query against a database for a customer, or uploading a file) without the need to provision or maintain the underlying infrastructure.

As code is triggered to run by an event (such as a customer clicking a link or submitting a file), infrastructure is spun up and code is executed, performing the required task. The underlying infrastructure is then spun down, leading to extremely low cost and simplistic architecture.

Why have APIs

By enabling APIs within your organisation you can improve the customer experience through new ways of interacting such as chatbots and mobile apps, improve data validity between systems and improve internal processes by streamlining data input processes or the retrieval of data.