Architecture Modernization in Legacy AWS Cloud-Native Systems
Learn how to modernize legacy AWS cloud-native systems using the Outbox Pattern with DynamoDB Streams, SNS, SQS, and Lambda to build reliable event-driven architecture.
Software Architecture: The Bad Parts
A practical walkthrough showing how seemingly reasonable architectural decisions can gradually turn a system into a big ball of mud. Learn about the Bad Parts of architectures.
Interviews Are Just a Random Process 🎲
You don’t know who you'll meet on the other side. You don’t know the company's mentality. You jump into unknown, into unknown organizational structure which often turns out to be chaotic, at best. Most importantly, you may face a person who doesn't necessairly wish you well.
Events are domain atoms
If you wonder how to take another step towards business language and its technical representation, then you should definitely read this article. You will learn how discovering of business capabilities combined with the vent sourcing and the decider pattern helps you in this challange.
Everything belongs to users
Homo Sovieticus's mantra was: Everything belongs to the kolkhoz, everything belongs to me. In the context of this text, I want to rephrase it to: Everything belongs to the app, everything belongs to users.
How easily get your DTO in TypeScript
Learn simple and effective ways to create DTOs in TypeScript for better type safety and data validation in your applications.
UX and Architect are two sides of the design
Programming is not the most essential part of the development process, but the collaboration is.
Every* system you develop is distributed, and Hermes PostgreSQL supports you in that
Pretending it is not exposes your client’s system to the unpredictability of the world’s reality.
Is SOLID dead?
I'll do a small revision of the SOLID principles, shifting it more towards high-level components and modern software development practices.
Be WET between modules, DRY within modules
Learn when to apply DRY vs WET principles in software architecture. DRY within modules for maintainability, WET between modules for decoupling.
Everything is a monolith
Do not harm yourself by thinking that you create a system with independent components
How teams fail to provide adequate quality
Learn why teams waste time applying unnecessary quality attributes and how to determine the right level of quality for your system's actual needs.
Overengineering by being a prisoner of patterns
Learn how being trapped by design patterns leads to overengineering. Discover the balance between coupling control and communication in software development.
False hope of various architectures from books
Why naming patterns as 'architectures' creates false hope. Learn the difference between implementation patterns and true software architecture.
Coupling management + Communication = Our job
Most of the known patterns can be reduced to the coupling control. Get to know how this reasoning can help you simplify your solutions.
Do not trust docs... and ORMs
Many documentations of different frameworks can deceive you because their creators are primarily interested in their interests, and sometimes, their knowledge and experience are limited. Read this article to prepare!
Comparing Time Availability archetype implementations
How to implement a time-based resource reservation system, assuming high traffic?
The ultimate solution to everything
If you do THAT, THEN YOU DO IT WRONG!
How to successfully deliver an MVP to the market
My thoughts on how we can help ourselves to successfully deliver the MVP on the market.
HL7 FHIR: Foundations in the architectural context
The common language for healthcare data exchange
Why make a decomposition of the monolith database?
Have you ever gotten stuck with your task because of a change introduced by another developer in a completely separate service?