Backlog for philcalcado.com

gistfile1.txt

Please write a comment with the order you'd prioritise these (and any suggestions or comments) 
or tweet to @pcalcado. <3

1. Why we moved from HTTP to Thrift(mux) in internal services

2. Moving from a one-size-fits-all API to one-api-per-client-application and 
its implications in a microservices archtiecture

3. We we moved on from numeric IDs to URNs and how do we manage object 
lifecycle in microservices architecture

4. A discussion on KPIs for non-product engineering teams?

5. Thoughts on feature teams and shared code bases, aka. Mobile apps 
are still monoliths

6. Tackling ownership problems in a microservices architecture

7. "How big are your microservices?" — A Discussion

8. Cambrian Explosion Post Mortem — Why and How we moved from "the 
best tool for the job" to "Let's make tool x the best for the job"

9. "Vulcanising Rubber" — Vertical integration vs. NIH

10. Microservices architectures need async programming

11. Moving Resiliency down in the Test Pyramid

12. The economics of microservices: what do you need to make this 
architecture feasible

2, 7, 10, 11, 12

5, 6, 11, 1, 3, 2, 8,10, 12, 7, 9, 4

3, 8, 6, 4

You could begin with 1, 2 and 3. They're great subjects!

1, 11 and 12.

4, 8.

1, 2, 3, 6, 7, 10, 12, 8, 5, 11, 9, 4

oo: 2, 6, 8, 12? they're all good.

3, 1, 2, 6, 7, 10, 11 in any order :)

great topics! I would particularly be interested in 12,11,4,8, and 5 (this is a prio'd order)

1, 6, 7