cd and the curse of legacy
TRANSCRIPT
When Legacy Strikes!!Achieving CD in large financial institutions
OutlineLarge, old organisations carry a lot of Legacy
- Systems
- Mindsets
- Contracts
Underfunding change
New things, old ways
These often kill “continuous” in its tracks
BioStarted in Enterprise Banking in 2004
Been working alongside dev teams implementing build, environment, deployment and testing automation since then
Internal systems, external customer facing systems
Run into common issues across organisations
“It is not necessary to change. Survival is not mandatory.”
Shared InfrastructurePhysical servers or VMs running many products/services
Ops team must deploy to prod or test
Disk space!
“Superficial Cloud”
Siloes Many built up over decades
Lead times can be days
No repercussions if SLAs are breached
Central teams become backlogged
Teams & ProjectsMany many projects and teams even across a single service/product
Feature branching is rife!
“Project” focussed on a release, then closes down
Focussed on features to the detriment of testing
Agile - but not Agile…
Designs often based on what’s happened before
SecurityBreakglass / jump servers
New s/w approvals
CAB
Network related - DNS, Load balancer
Internal information systems
Game over?Not quite …
Lot to do …
Know what to expect …
Know your landscape …
Pick your fights …
Choose your team.
There is change...Evolutionary not Revolutionary …
Slow incremental change …
They watch each other …
Big budgets continue to be allocated to “Digital Transformation”
DevOps
New shapes and types of vendor & platform
Trying more new things
Pockets of “success”
