DevOps

in a Serverless World

Linda Nichols

@lynnaloo

Norfolk,VA

norfolk.js

Virginia is for Lovers

Serverless

^

Virginia is for Lovers

Serverless

^

But there are servers?

Thank You Nashville!

Let's Talk About Serverless...

and Developers

with a little help from...

1988

https://github.com/lynnaloo/1988

Developers Have Lots of Opinions

They Love Process and Best Practices

• Their favorite editor
• Their favorite language
• Their favorite frameworks
• A code formatting tool
• Formatting tool for code prettiness
• Real-time static code analysis

Developers Want (need):

Vim

VS Code

Emacs

Atom

IntelliJ

Visual Studio

Eclipse

Notepad

Lint

Prettier

editorconfig

pylint

eslint

Mechanical Keyboard

Stack Overflow

Java

.Net

npm

nuget

Ruby

CoffeeScript

Python

Rust

TypeScript

yarn

• Pair-programming
• Very-opinionated testing framework
• Unit tests
• Integration tests
• Code coverage up to 90%

Then Test the Code:

Wait, should we have written the tests before the code?!?

• Very-opinionated revision control system
• Current popular branching strategy
• Squash those insignificant commits
• Very detailed commit messages
• Branch names match the task

Then Commit the Code:

Github

Gitlab

Visual Source Safe

Bitbucket

Gitflow

Github Flow

Subversion

CodeCommit

GitOps

• Push the code to a dev branch
• Issue a pull request
• Make sure all of the tests are passing
• Request a code review

Merge the Code into Master:

Your branch isn't up to date??

Why aren't the tests passing?

Why did you use tabs and not spaces?

Squash those commits!

The linter is failing!

Sometimes, reviewers can be tough.

OK, LGTM. Merged.

Cue the CI/CD Tool:

Travis CI

Azure Pipelines

Gitlab CI

Jenkins

Circle CI

Bamboo

CodeDeploy

Flux

Github Actions

LaunchDarkly

CodeBuild

Now the code is being deployed to a staging environment for more testing

What about Serverless?

Serverless is for Developers

Serverless is for Developers

• Event-driven architecture
• Support for most programming languages
• Focus is on code, not infrastructure
• Built-in services and libraries means less code
• FaaS naturally map to microservices

What's the Development Process?

Pre-recorded Demo Time

Unfortunately, no service is fully-managed enough to format, test, and debug your messy code.

So, why do those who hold process so dear, throw it all away when they build cloud-native apps?

Because serverless application development is new and can be a little scary.

But all of the development practices that we love, still apply in a serverless world.

and there are many, many new tools and services to support your process.

Demo

https://github.com/lynnaloo/1988

My Toolset

Conclusion

• No-ops does not mean no DevOps
• FaaS is not revision control
• Testing in prod isn't testing
• Abstraction is not CI/CD
• Don't abandon what's important

Conclusion

Thank you

@lynnaloo

Credits

Travis Webb

YOLO Programmer