Compares processes with Berlioz and traditional approaches.

1. from code to production in no time
https://berlioz.cloud
ruben@berlioz.cloud github.com/berlioz-the
https://slack.berlioz.cloud
by Ruben Hakopian
@rubenhak @berlioz_cloud

2. Area Action Dev Effort Dependencies With Berlioz
Build / Packaging Manual / custom
script
ongoing 1 command
Local Run Manual / custom
script / docker
compose
ongoing 1 command (to
build and run)
Infrastructure setup Manual / custom
script
ongoing SRE might help automatically
Run (in cloud) Manual / custom
script
ongoing SRE might help 1 command
Monitoring Not available SRE might help automatically
Cross-Team
Dependencies
Collect instructions
from other teams
Ongoing Other teams 1 command,
Clear view of
dependencies

3. Area QA Effort Dependencies With Berlioz
Infrastructure setup Ongoing Dev & SRE 1 command
Running Ongoing Dev & SRE 1 command
Monitoring Ongoing Dev & SRE automatically

4. Area SRE Effort Dependencies With Berlioz
Build/Packaging Initial* Dep on dev 1 command
Infrastructure setup Initial* Dep on dev automatically
Customization Ongoing Dep on dev Freedom to customize
using policies
Deployment Initial* Dep on dev 1 command
CI/CD Initial* Dep on dev Standard CI/CD template
Monitoring Initial* automatically
* Initial becomes ongoing effort if changes are made to design/dependencies.

5. https://berlioz.cloud
ruben@berlioz.cloud
github.com/berlioz-the
https://slack.berlioz.cloud
@rubenhak @berlioz_cloud
Ruben Hakopian