Getting to the post-industrial age of DevOps

Transcript

1. Getting to the post-industrial age of DevOps
2. Nick Bruun github.com/nickbruun @nickbruun bruun.co CTO @ Iconfinder Fairly carnivorous
3. 1. The good old days 2. The renaissance man’s DevOps 3. The industrial revolution of DevOps 4. Trouble in DevOps paradise 5. The post-industrial age of DevOps
4. The good old days
5. Database Application Web server Files Ops Dev
6. … but, then something happened
7. Scale
8. Scale
9. “Agile”
10. Complex stack Web server Database memcached Redis ElasticSearch RabbitMQ
11. Leaky abstractions Mandatory Spolsky-ism
12. The renaissance man’s DevOps
13. Dev Ops
14. DevOps
15. “Let’s work together”
16. (very often) became
17. “We all do everything”
18. Architecture Development QA/testing Operations System administration Database administration Full-stack developer h4x0r ninja!11
19. Inefficient
20. Jack of all trades, master of…
21. The industrial revolution of DevOps
22. Automation
25. Tooling
28. Trouble in DevOps paradise
29. “So… what do you do for a living?”
30. Servers are still servers Databases are still databases Infrastructure is still infrastructure
31. Servers are still complicated Databases are still complicated Infrastructure is still complicated
32. “I need a PostgreSQL database” Let’s pretend…
33. An Ops person would: 1. Be grumpy, ask questions 2. Provision server(s) 3. $ sudo apt-get install postgresql-server 4. Set up replication, monitoring, logging and backups 5. Hand over an IP and a port to the Dev The Good Old Days
34. Some random person would: 1. Provision server(s) 2. Pour over the manuals 3. $ sudo apt-get install postgresql-server 4. Set up replication, monitoring, logging and backups 5. Yay, database! The renaissance man’s DevOps
35. Some random person will: 1. Provision server(s) 2. Find a Chef cookbook or Puppet module for PostgreSQL and hopefully monitoring/backup/replication 3. Run configuration management 4. Debug why things aren’t working (read the manual) 5. Yay, database! The industrial age of DevOps
36. But, what if… “The primary went down”
37. But, what if… “We need a bigger server!”
38. Oh dear God…
39. The Post-Industrial Age of DevOps? How do we get to the
40. How do we get to do, what we do best? … or,
41. As a developer, I will: 1. Click a button or run a command to get a PostgreSQL server 2. Get back to work The Awesome Way™
44. Service-ification noun the encapsulation of everything as services
45. Service-ification noun the encapsulation of everything as services ≠ Service oriented Architecture
46. Services and service providers
47. Redis as a Service PostgreSQL as a Service ElasticSearch as a Service Load balancer as a service Application #1 Application #2 Application #n ..
48. Application runtime as a Service Redis as a Service PostgreSQL as a Service ElasticSearch as a Service Load balancer as a service Application #1 Application #2 Application #n ..
49. Are we there yet?
50. Is running infrastructure our core business? Let’s ask ourselves…
52. “But… X as a service is expensive!”
53. “But… I don’t trust them!”
54. Platforms are hard
55. Encapsulation/isolation
58. Resource management
60. Orchestration
61. Kubernetes
62. Resource management Encapsulation/ isolation Orchestration
65. Flynn
67. Metal
68. We have a long way to go In other words…
69. So, why not go back to the good old way?
70. Focus
71. Security
72. Resource utilisation $
73. Uniformity
74. Peace of mind
75. Let’s get cracking!
76. thx