devops & standards - why standards matter
TRANSCRIPT
Why standards matterAngad Singh@angadsg
DevOps
Architecting (micro)services
Infrastructure Automation
Developer Productivity
DevOps
Debugging all layers
Incident Management
Cost Management
Shared Libraries aka Reusability
E.g.Redis/MySQL/xyz connection manager
In memory cachingImage transformations
Security
E.g.Consistent Firewall rules
Standard input sanitizationCentralized Alerting
Developer Productivity
No surprises when navigating the system
e.g.All services log to /var/log
One deploy toolchain to rule them all
Cost Optimization
Engineering cost > Infrastructure cost
Better Standards = Lesser Engineers
CI/CD
Standard pathway for all servicesUnit Tests
Integration Tests
Engineering Onboarding
Start early, start better.
Raise the bar with new hires.
Consistent Naming Service name = Docker name = Repo name
= monitoring namespace = load balancer name = CI name
Standard Provisioning
Ansible/Chef etc.
Docker - use and throw.
Standard Configuration
Consul, Zookeeper etc.
Hot reloadable configurationDeploy faster, fix faster
DevOps as a Shared Bus
Identify patterns across all services
Easier to handle complexity of microservices
Ability to debug at any level
DevOps as a Shared Bus
Small teams with more context and communication are better than large teams with no communication
Work closely with developers
Enforce Standards
But with logic and common sense.
(and some love, for our developers)
Its all about Give and Take.
(Take sudo, Give advice)
