Architecture Weekly Issue #23. Articles, books, and playlists on architecture and related topics. Every record has the complexity indication: π€ means hardcore, π·ββοΈ is technically applicable right away, Β πΌ - introduction to the topic or an overview. Now in telegram as well.
WARNING πΊπ¦
It's already 4 months of crazy, inhuman, unjustified war of Russia against Ukraine. We condemn this war and want it to stop ASAP. We continue this newsletter so you can advance your skill and help the millions of Ukrainian people in any way possible.
Diagrams as Code 2.0 π·ββοΈ
As we love PlantUML and C4 Model, it's time to share a just published talk from GOTO 2021 conference from the last year. Simon Brown talks about the diagramming as code, starting with the value of C4 and then proceeding to the benefits of switching from just lines and errors to creating diagrams with code and showing the tools you can do it with.
DrivenCon - Sponsored
If you're managing the engineers or want to try an engineering management track, you might want to attend the online conference DrivenCon for engineering managers. Interactive zoom sessions, engaging networking with experts, gamification and many more!
Architecture Competency πΌ
IASA Global is an association for all IT Architects. In this article they describe their Competency Model for Architects: 5 pillars which consists of skills every competency is measured by a level and has its learning objectives. Very interesting read about the competencies the Architect should posses.
Solution Architect Roadmap πΌ
Speaking about competencies, can not skip the solution architect roadmap built by myself. It includes both roles the architect may play on the project and skills that architect should have. PRs are welcome!
A standardized, specification-driven API Lifecycle πΌ
A transcript from Kin Lanes talk on how API Lifecycle is driven by the specification. The APIs are born, discussed, used, deprecated and removed; but if we look deeper we will find out that one of the key driver of such lifecycle is the specification in the form of OpenAPI or AsyncAPI. Look more in the transcript.
Resources to Learn Architecture and System Design π·ββοΈ
We previously included a couple of articles of Shivang, for example on Vitess used by YouTube; now we share a digest of resources to learn Architecture and System Design done by him. A lot of books and courses inside.
Spotify Live architecture description π·ββοΈ
Spotify allows to create a live audio room and then republish the result as a podcast episode. On their blog Spotify describes how they implemented the feature and show the components required for it and the data flows within it.
Service Architecture at SoundCloud π·ββοΈ
SoundCloud have their own technical blog as well. This series is about their approach to Service Architecture. They started with Backend for Frontend Pattern, then migrated to Value Added Services and then introduced Domain Gateways. Valuable story in the series.
On making architectural decisions π·ββοΈ
Short article on making architectural decisions. The main take away is that you can evaluate the difference attributes of the decision using estimates or coefficients, but this is not sufficient; since they are only meaningful in a broader context; which is usually the main problem to define.
Consistency Models and Baseball π€
An insightful report by Microsoft showing different consistency models with a help of baseball. The paper introduces a sample application which simulates a baseball game and then describes how it can be seen from a different perspectives given different guarantees.
Testing Pipeline for Frontends π·ββοΈ
Ramona published a long, but nice article on the pipelines for Frontend applications. She touches the testing pyramids, continuous integration and delivery pipelines and even provide a short recipe on how to set it up on Github Actions. Smashing Magazine blog delivers again.