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.
Read more »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.)
Read more »My notes on GΟΤΟ 2014 - Microservices - Martin Fowler
Characteristics of Microservices
Componentization
Organized around business capabilities
Products not Projects
Smart endpoints and dumb pipes
Decentralized Governance
Decentralized Data Management
Infrastructure Automation
Design for failure
Evolutionary Design
With services we typically use some kind of interprocess communication facilities such as web service calls or messaging or something of that kind.
How big should a microservice be?
"It should have one responsibility" --too vague
Read more »Hey, I passed the "Java SE 8 Programmer I" exam and received the "Oracle Certified Associate" certification.
Here is the link to the certification:
https://www.credly.com/badges/97c9a618-181d-406f-918e-46d68cbcd782
Now, I do not know how trust-worthy this credly.com thing is, and archive.org is telling me that it has never captured the above page, so, here it is in image form:
