With system requirements changing, along with complex logic and NFRs, our team wrote and tested application logic, deployments and system architecture as code. Using Kanban, everyone contributed to tasks, picked up the priority work and delivered beyond the traditional separation of coding jobs, testing jobs, and DevOps jobs. Check out this description from a project review:
“A series of stateless deterministic processors written in Python and Java, with UI/service aspects in Node/React, driven using RabbitMQ, storing data into PostgreSQL and a JanusGraph database, with balancing and service registration using NginX and Consul, continuously integrated onto an architecture built to scale using Nomad, Terraform and Docker, with a underlying provider of AWS, monitored using MetricBeats.The Result is a DevOps environment built for future enhancements, continuous improvement and tuning, with healing and scaling to tackle future challenges and volumes.”
It’s great when the team solve the problems they are presented with. They see all of the problem and don’t just focus on one part of the solution.
