The document discusses whether people are still using microservices and some of the tradeoffs and challenges of using microservices architectures. It notes that microservices are one of many architectural patterns and that distributed systems are harder to build robustly than single-machine systems due to increased failure rates. The document questions whether certain attributes originally associated with microservices like versioning, continuous integration jobs, and endpoints may be given up in favor of other attributes and technologies.

1. AreYouStillDoing
Microservices?
Philipp Krenn @xeraa

2. https://opentelemetry.io/docs/demo/architecture/

3. https://opentelemetry.io/docs/demo/architecture/

4. TheBestThingSince
@xeraa

5. TheWorstThingSince
@xeraa

6. ItDepends
@xeraa

7. OneofManyArchitectural
Patterns
https://en.wikipedia.org/wiki/
List_of_so!ware_architecture_styles_and_patterns
@xeraa

8. FetishontheDeploymentUnit
@xeraa

9. MicroserviceSize
Nano, Pico, Femto, Atto, Yocto
@xeraa

10. "NotesonDistributedSystemsfor
YoungBloods"
https://www.somethingsimilar.com/2013/01/14/notes-on-
distributed-systems-for-young-bloods/
@xeraa

11. Distributed systems are different
because they fail o"en
Writing robust distributed systems
costs more than writing robust single-
machine systems
@xeraa

12. Robust, open source distributed
systems are much less common than
robust, single-machine systems
Coordination is very hard
...
@xeraa

13. GivingUpOnSomeAttributes
@xeraa

14. !
Version
@xeraa

15. !
Build&CIJob
@xeraa

16. !
Endpoint
@xeraa

17. !
Process
@xeraa

18. WinningOtherAttributes
@xeraa

19. AlltheTechnologies
@xeraa

20. AreYouStillDoing
Microservices?
Philipp Krenn @xeraa