The deck for Practical Microservices as presented at YOW 2013 in Brisbane. Minor changes from the Melbourne event.
Bonus point if you can spot the typo!
160. TIP: Standardise in the gaps between services - be
flexible about what happens inside the boxes
TIP: Avoid RPC-mechanisms or shared serialisation
protocols to avoid coupling
TIP: Have one, two or maybe three ways of
integrating, not 20
TIP: Pick some sensible conventions, and stick with
them
@samnewman
161. TIP: Capture metrics, and logs, for each node, and
aggregate them to get a rolled up picture
TIP: Use synthetic transactions to test production
systems
TIP: Avoid distributed transactions if at all possible
TIP: Use correlation IDs to track down nasty bugs
TIP: Abstract out underlying platform differences to
provide a uniform deployment mechanism
@samnewman
162. TIP: Have a single way of deploying services in any
given environment
TIP: Consumer Driven Tests to catch breaking changes
TIP: Don’t let changes build up - release as soon as
you can, and preferably one at a time!
TIP: Use timeouts, circuit breakers and bulk-heads to
avoid cascading failure
TIP: Consider Service Templates to make it easy to do
the right thing!
@samnewman
164. TIP: Standardise in the gaps between services - be
flexible about what happens inside the boxes
@samnewman
165. TIP: Standardise in the gaps between services - be
flexible about what happens inside the boxes
@samnewman
166. TIP: Standardise in the gaps between services - be
flexible about what happens inside the boxes
TIP: Don’t let changes build up - release as soon as
you can, and preferably one at a time!
@samnewman
167. TIP: Standardise in the gaps between services - be
flexible about what happens inside the boxes
TIP: Don’t let changes build up - release as soon as
you can, and preferably one at a time!
@samnewman