Achieve performance engineering and testing at the end of every sprint
Get hands-on experience with continuos integration using the latest versions of the most popular DevSecOps tools, all working together, end-to-end, in a set of servers participants control.
NOTE: Content here are my personal opinions, and not intended to represent any employer (past or present). “PROTIP:” here highlight information I haven’t seen elsewhere on the internet because it is hard-won, little-know but significant facts based on my personal research and experience.
Only this course provides participants a full set of several cloud-based servers to work on live during the class. This is an opportunity few get even with on-the-job experience.
See how the 21 groups of DevOps technologies work together in a complete toolchain that builds and deploy software: AWS CLI, Git, GitHub/GitLab, Maven/Yarn, Nexus, Jenkins/Cloudbees, Vault, SonarQube, Selenium, Terraform.
Commentary during this “guided tour” include tips and tricks for moving organizations to the end-state shown – for deep insight into both benefits and challenges related to agile automation in DevSecOps.
The “Sec” part of “DevSecOps” means security, which include scans of code for vulnerabilities, use of digital certificates to control access, and tools to manage secrets using secure vaults.
To ensure quality at speed, Agile software developers are increasingly required to include in each sprint automated performance status in their System Demo presentations.
The traditional approach of performance testing only before final release to production means that potentially major risks and technical debt can remain hidden. Here is how organizations make performance testing and engineering “shift-left” earlier in the software development lifecycle.
Who Should Attend
This course is for anyone new to DevSecOps but experienced with information technology and software development. No specific prerequisites are assumed, and new technical concepts are explained. Executives, directors, managers, product owners, analysts, testers, programmers can all benefit from this first-hand experience.
Editions of the course
There are several editions of this class, of different length:
The half-day introduction provides an understanding of key DevSecOps buzzwords and concepts possible only from seeing the various tools all working together. Participants pull from then push to GitHub, edit files, and see first-hand programs built and software tested automatically. Participants leave with an understanding of the meaning behind buzzwords and abbreviations in DevSecOps.
The full-day experience has you generating both application code and the whole DevOps toolchain for an architecture that automatically scales. You then re-build the whole setup after making configuration changes. Participants leave with an ability to identify DevSecOps toolchain components and usage workflow and have an appreciation for some of the subtleties about each technology.
The two-day immersion enables you to see code moving through multiple environments from development servers to production clusters – crucial for working in corporate enterprises. Participants see a live “blue/green” deployment and fall-back. Participants leave with a visceral understanding of both the advantages and limitations modern DevSecOps offers.
Example: Maven vs. Yarn
GitHub/GitLab source repository
Maven/Yarn package repository
Nexus binary repository
SonarQube status repository
CMDB server repository
DNS (Domain Name System)
CDN for files around the world
Application SQL databases
Liquibase database schema changelogs
Programming Languages (Java)
Java Frameworks: Spring Boot
Build and Release
Release when ready
Docker images vs. Vagrant
AWS HVM machine images
SonarQube code scan run reports
Failover test run
Browser inspect debugger
ELK stack vs. Tick stack
Elsticsearch vs. InfluxDB
Logstash vs. Telegraf
Kibana vs Graphana
More on DevSecOps
This is one of a series on DevSecOps:
- ci-cd (Continuous Integration and Continuous Delivery)
- User Stories for DevOps
- Git and GitHub vs File Archival
- Git Commands and Statuses
- Git Commit, Tag, Push
- Git Utilities
- Data Security GitHub
- GitHub API
- Choices for DevOps Technologies
- Pulumi Infrastructure as Code (IaC)
- Java DevOps Workflow
- AWS DevOps (CodeCommit, CodePipeline, CodeDeploy)
- AWS server deployment options
- Cloud services comparisons (across vendors)
- Cloud regions (across vendors)
- Azure Cloud Onramp (Subscriptions, Portal GUI, CLI)
- Azure Certifications
- Azure Cloud Powershell
- Bash Windows using Microsoft’s WSL (Windows Subsystem for Linux)
- Azure Networking
- Azure Storage
- Azure Compute
- Digital Ocean
- Packer automation to build Vagrant images
- Terraform multi-cloud provisioning automation
Hashicorp Vault and Consul to generate and hold secrets
- Powershell Ecosystem
- Powershell on MacOS
- Jenkins Server Setup
- Jenkins Plug-ins
- Jenkins Freestyle jobs
- Docker (Glossary, Ecosystem, Certification)
- Make Makefile for Docker
- Docker Setup and run Bash shell script
- Bash coding
- Docker Setup
- Dockerize apps
- Kubernetes Operators
- Threat Modeling
- API Management Microsoft
- Scenarios for load
- Chaos Engineering
Wait, there’s more. Click one of these …
This article is one of a series about tuning and performance:
- Performance testing in the cloud era
- Perftest (Performance Testing and Engineering)
- Agile Performance Testing and Engineering
- Build load-balanced servers in AWS EC2 using CloudFormation
- JMeter in the cloud for distributed performance testing
- TruWeb performance testing on macOS and Linux clients
- LoadRunner 12.55 installation
- WebTours configuration in LoadRunner and others