My notes on Devoxx 2016 Belgium - Microservices Evolution: How to break your monolithic database by Edson Yanaga (I attended this conference)

Reduce maintenance window

Achieve zero downtime deployments

“Code is easy, state is hard”

Changes in a database schema from one version to another are called database migrations

Tools: Flyweight Liquibase

Migrations require back and forward compatibility

Baby steps = Smallest Possible Batch Size

Too many rows = Long Locks

My notes on Devoxx US 2017, Knowledge is Power: Getting out of trouble by understanding Git by Steve Smith

“If that doesn’t fix it, git.txt contains the phone number of a friend of mine who understands git. Just wait through a few minutes of ‘It’s really pretty simple, just think of branches as…’ and eventually you’ll learn the commands that will fix everything.”

My notes on GOTO 2016 - Microservices at Netflix Scale: Principles, Tradeoffs & Lessons Learned - R. Meshenberg

They have a division making a layer of tools for other teams to build their stuff on top of it.

Exceptions for statelessness are persistence (of course) but also caching.

Destructive testing - Chaos monkey -> simian army - in production, all the time. (During office hours)

Their separation of concerns looks like a grid, not like a vertical or horizontal table.

My notes on GOTO 2015 - Progress Toward an Engineering Discipline of Software - Mary Shaw

Notes

17:28 past the bridges and into software engineering

Software Engineering is all design. Production used to be printing the CDs, and nowadays it is hitting the “deploy” button.

“scaling the costs to the consequences” – the point is not to minimize the cost, the point is to scale it to the consequences. Risks must be taken, and if the potential gains are huge, then the risks can be correspondingly large.

My notes on GOTO 2015 - DDD & Microservices: At Last, Some Boundaries! - Eric Evans

Microservices and Netflix - what is the connection?

Isolated data stores

“A service is something that can consume messages and can produce messages”

My notes on GOTO 2014 - REST: I don’t Think it Means What You Think it Does - Stefan Tilkov

“People decide they want to build something in a RESTful fashion, so they spend all their time arguing about where the slashes go”.

“It is the first litmus test for your REST API whether you depend on specific characters in your URIs for things to work.”

(From the client’s point of view.)