My latest articles on software architecture and software engineering
- Simple but effective architectural decisions documentation with ADRs, PRILER framework and MarkdownGiven the context of evolvable software architecture and agile projects, documentation must be concise, clear, effective and… constantly changing. Nobody wants to โฆ Read more
- Make stakeholders lives easier with the 4+1 view modelHow to describe software architecture in a way that can be easily understood by all stakeholders, be they technical or non-technical? How โฆ Read more
- DRY principle with MicroservicesWhen working with development teams transitioning from a monolithic applications to microservices I sometimes face their anxiety of breaking the ๐๐ฅ๐ฌ (๐ฑ๐ผ๐ป’๐ โฆ Read more
- Layer Architecture vs. Hexagonal Architecture. Which one to choose?Layered architecture is a common architectural pattern for organising application components into distinct technical layers – presentation, application, business, persistence, etc The โฆ Read more
- 4 database caching strategies for scaling applicationsWhen ๐๐ฐ๐ฎ๐น๐ถ๐ป๐ด ๐ฎ๐ฝ๐ฝ๐น๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป๐ the database is often one of the bottlenecks. Caching is an effective way of reducing load on the database โฆ Read more
- What is MACH Architecture?You may have heard this acronym and you were wondering that it means. MACH is an industry tech standard describing modern technology. โฆ Read more
- Prototyping with headless CMSOne easy way I sometimes validate software architectural solutions I am working on is through ๐ฝ๐ฟ๐ผ๐๐ผ๐๐๐ฝ๐ถ๐ป๐ด. According to wikipedia, a prototype is โฆ Read more
- 3 simple rules for effective communicationEffective communication can prevent or even overcome many problems in software engineering. Many engineers are often underestimating the value and the power โฆ Read more
- Data isolation in multitenant applicationsIsolating data in multitenant SaaS applications is a challenging aspect. Between the extremes of sharing all resources between tenants and provisioning individual โฆ Read more
- The six drivers for evaluating legacy systemsThere is no silver bullet method for legacy modernization. The best approach obviously depends on the problem that need to be solved. โฆ Read more
- Untangle Complexity With Event StormingUnderstanding complex domain models is quite challenging. You can spend a huge amount of time chatting, emailing or meeting relevant (and sometimes โฆ Read more
- Software Architecture Evaluation MethodsHere is yet another post on software architecture evaluation. After ATAM, LAE, Tactics Based Analysis, this time a more general one focusing โฆ Read more
- 12 common pitfalls of legacy modernizationFor sure the majority of us working long enough in software engineering have been involved in at least one legacy modernization project. โฆ Read more
- Tactics-Based Analysis for Software ArchitectureA tactic is a design decision which influences the achievement of a quality attribute response. It directly affects the systemโs response to โฆ Read more
- Lightweight Software Architecture EvaluationContinuing the series of posts on software architecture evaluation, with a simpler evaluation method: Lightweight Architecture Evaluation (LAE). As documented in Software โฆ Read more
- ATAM made easyWe all know that reducing risks in early phases of software development lifecycle is extremely important. We all agree that we must โฆ Read more