OutSystems DevOps Model Series: 1-Introduction
This article is the first one of a series that will talk about DevOps Model within OutSystems
As it is bigger than usual, I thought it would be nice to start with the main objective.
At the end of this article, you will know how to properly define a model to work in a large OutSystems factory with multiple squads and projects co-existing and also how to support your apps while keeping a simple continuous delivery approach in a secure and organized way with Lifetime.
We will talk about:
- Access Control Policies
- Release Management Cycles
- Support process
- And more
If this is what you are looking for… keep reading.
First of all. Let’s talk about definitions!
What is DevOps?
Our most famous “common sense definitor” Wikipedia defines it as:
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps is complementary with Agile software development; several DevOps aspects came from the Agile methodology.
Amazon AWS in the other hand says:
DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market.
If we look in the internet, we have all sort of definitions for the term DevOps.
However, none of them is an official definition. The truth is that it doesn’t have a universal definition yet.
Anyway, we can agree that it is a mix of processes and methods to enhance the agility of delivery according to most definitions.
And how OutSystems helps with that?
If you know OutSystems well, you may also know that one of the definitions for it is: full-stack & full lifecycle platform.
By full lifecycle, they mean that OutSystems already delivery a way to easily promote your code across different environments doing its own impact analysis.
What we can call a simple delivery pipeline.
Even if it lacks a integration layer for automated tests out-of-the-box, it still is a very powerful tool to help with deployments and can be called a simple tool for CD (continuous delivery).
All this is done using LifeTime, a very powerful default tool that OutSystems provides as part of their license.
However, as spider man’s uncle Ben used to say:
“With great power comes great responsibility”
And because of that we need to make sure this powerful tool is well configured and capable of doing everything that we need while ensuring security and scalability.
So… Let’s begin our journey and see what we need to make it happen.
On the next article we will talk about the requirements for this model we are proposing.
Next: 2 — Requirements
OutSystems DevOps Series Articles:
Disclaimer: Most of the material was gotten from OutSystems documents
