Learnings
Boost your knowledge with the insights from our expert team.
Amazon's Prime Video moved from a servless / microservices architecture to a monolith application. It helped them achieve higher scale, resilience, and reduce costs.
A Gentle Introduction to Islands
Nurturing Design in Your Software Engineering Culture
Looking Beyond the Hype: Is Modular Monolithic Software Architecture Really Dead? tl;dr: NO!
Import Linter allows you to define and enforce rules for the imports within and between Python packages.
Software architecture patterns: Take a deep dive into several common software architecture patterns
If one is seeing a lot of Accidental Difficulty caused by boiler-plate code or hand-written translations to and from tools and interfaces, something in the system is likely Simply Simplistic. Simply Simplistic models and services and interfaces are too simple, failing to capture the Essential Difficulty, and thus force the Essential Difficulty to be duplicated by each user, increasing the Accidental Difficulty with each duplication. Sometimes you can extract this Accidental Difficulty into a library or helper Once And Only Once. Sometimes you cannot. If you cannot, your language tool may be Simply Simplistic itself, subject to the Missing Feature Smell.
Simplistic protocols and models and language features can end up becoming complexity multipliers because the complexity is duplicated by each and every user of the model or protocol. They are also effort multipliers. Fortunately, one can sometimes solve this problem by wrapping or refactoring the protocol or model or language feature within a library to utilize it, thus capturing the Essential Complexity into the library and thus creating the feature/language/model that should have existed in the first place.
Preventing Data Loss When Using Messaging:
Software Architecture Monday with Mark Richards is a free bi-weekly software architecture lesson containing a short video about some aspect of software architecture. These lessons contain tips, techniques, and advice to help you in your journey from developer to architect.
Code Colocation is King: keep the code that changes together close together
Reliable Microservices Data Exchange With the Outbox Pattern:
Airbnb's Journey To A Service-Oriented Architecture At 1,000-Engineer Scale
The strange world of Python, as used by big investment banks:
Disasters I've seen in a microservices world:
Django API Domains
Ideas and inspirations from The Architect of Modern Algorithms
Write code that is easy to delete, not easy to extend.
Architecture and Design InfoQ Trends Report
Excellent article about the trade-offs of Monolith, Microservices, Nanoservices, and Monorepo. Where Do You Want Your Complexity?
Overly defensive programming
Classic article about the cost of wrong abstractions in programming:
Applications age like fish, data ages like wine:
