Welcome to NoOps, the new DevOps!

Implementing DevOps best practices is a daunting task when you don’t know where to begin. What's more, even after implementing best practices, scaling them as your developer teams and projects grow is often an even bigger challenge.

What if you can just skip DevOps altogether?

Welcome to the world of NoOps, where DevOps is no longer relevant...

In this session we are going to present real examples from different agencies who have adopted and realized first-hand, the value and benefits of the NoOps approach.

This session will cover:

Why it’s ok (and not scary) to say goodbye to DevOps
How these agencies replaced DevOps with the NoOps approach
Lessons learned in adopting NoOps in their teams and projects
The top benefits they’ve seen and the performance metrics

This session is for developers and developer management of all levels.

Transcript

1. NoOps, the new DevOps Drupalcon Nashville, Wednesday 11th April 2018 15:45 - 16:45 Room 101D Kieron Sambrook-Smith, Chief Commercial Officer, Platform.sh kieron@platform.sh Scott Hooker, TES Global, Principal Engineer scott@tes.com Winn Jewett, Founder, Oxbow Labs winn@oxbowlabs.com
2. • Kieron Sambrook-Smith Chief Commercial Officer, Platform.sh • Scott Hooker Principal Engineer, TES Global • Winn Jewett Founder, Web Architect, Oxbow Labs AGENDA
3. Contributing to competitive advantage • It’s about getting your edge out there quicker • Process and DevOps • Process improvement means less, but more work ! • Doing DevOps better • Why not NoOps ! • The future of Platform.sh • ‘Idea to Cloud’ application platform
4. • Kieron Sambrook-Smith Chief Commercial Officer, Platform.sh • Scott Hooker Lead Drupal Developer, TES Global • Winn Jewett Founder, Web Architect, Oxbow Labs AGENDA
5. Who • Tes Global is a digital education company committed to supporting teaching and learning. Our mission is simply to help teachers, schools and universities succeed. • Remote first (definitely has its challenges) • Mixture of Drupal and node (even more challenges).
6. All the apps
7. Development workflow
8. • Onboarding down from 3-4days to 3-4hours. • Not just time that the new starter is losing, it’s time that I’m losing having to hand hold. • Push code to production on day 1. • No time spent in dev ops • Opportunity cost - less time refactoring for performance, more time building features that our users love. Productivity
9. Honestly this is how we do things.
10. Services with no set up. Finally.
11. But will it scale?
12. But will it scale?
13. What I’d like to see soon... • So the time suck of onboarding people has gone • I don’t have to care about server performance any more. Just my application. • Still caring about how people run the sites locally… I’d like that to stop.
14. Conclusion • I get to do what I enjoy. • Write code. Build features… • Contribute to opensource.
15. • Kieron Sambrook-Smith Chief Commercial Officer, Platform.sh • Scott Hooker Lead Drupal Developer, TES Global • Winn Jewett Founder, Web Architect, Oxbow Labs AGENDA
16. • Winn Jewett - Founder, Web Architect • Founded 2005 • 5-person team • 90% Drupal since 2010 Who and why?
17. Our Clients • About 50 small clients • A handful of enterprise clients Background Information
18. Technical Challenges • Dedicated server cluster • All small to medium websites hosted in one environment • Drupal 6 & 7 side-by-side • One version of PHP, MySQL, Varnish, etc… • Shared performance experience Result: Many sleepless nights Old School Hosting
19. Business Model • Fixed-price servers + unlimited* clients = profit ◦ * unlimited != unlimited • As website numbers increase, performance slows, and more hardware is needed, negating any potential profits Old School Hosting
20. Hosting Options Standard Platform.sh • Standard hosting, with Small, Medium, Large sizes Enterprise Hosting • Enterprise projects use an identical development workflow, with stage and prod on a separate server cluster Self-Hosted • Develop on Platform.sh. Deploy to anywhere. Workflow With Platform.sh
21. One Workflow Fits All • Clean and simple, for small projects Workflow With Platform.sh
22. One Workflow Fits All • Feature-based branches for large projects Workflow With Platform.sh
23. App Configuration File • Sanitizes all dev and feature environments • An environment variable defines which environments are sanitized
24. Configuration via .platform.app.yml file Time Savings
25. Lightning-Fast Security Updates • We deploy security updates to 50 websites in 30 minutes > platform multi -p [project 1],[project 2] 'branch sa-2018-002 master' Time Savings
26. Don't Commit Drupal Code • Use Drush Make files in D7 • Composer in D8 Time Savings
27. Platform CLI Examples > platform get (Create a local copy of the project) > platform build (Build a project locally) > platform multi -p [project 1],[project 2] 'branch sa-2018-002 master' (Create a new branch on multiple projects) > platform ssh 'sudo rm -rf .' (Execute any command on the server, and display the results) > platform drush cr --environment=stage (Execute a drush command on the server) Time Savings
28. Example: Fixing a bug on a new (to me) site > platform get (Prompts to select a project) > platform build > platform branch hotfix > platform checkout hotfix > sudo fix_my_code > git commit -am 'crisis averted' > git push (Rebuilds the environment) > platform merge Total Time: ~6 minutes Time Savings: about 2 hours Time Savings
29. Free SSL Certificates via Let's Encrypt • Total Time: 1 minute adding https to routes • Time Savings: 1-2 hours Onboarding a New Developer • Total Time: ◦ 10 minutes, from a technical perspective ◦ Greatly reduced, from a training perspective • Time Savings: 1-2 days Time Savings
30. • Reduction of overhead through consistent workflow • More time spent on billable hours • Hosting plans are more competitive • Faster turn-around on quick fixes and security updates • Better quality code, resulting from feature-based branches Conclusion
31. THE END! Q&A?