SOAP (Simple Object Access Protocol):💡 Description: A protocol for exchanging structured information in web services. It relies on XML for message format and usually operates over HTTP or SMTP.🔦 Use Cases: Enterprise-level applications requiring high security and transactions, such as banking and payment processing.REST (Representational State Transfer):💡Description: An architectural style that uses HTTP requests to...Read More
Building scalable microservices requires the right set of tools to ensure seamless communication, security, and deployment. This guide covers the core technologies used in microservices architecture.1. DatabasesSQL databases like MySQL and PostgreSQL ensure structured data management, while NoSQL options like MongoDB and Cassandra offer scalability for unstructured data.2. Message BrokersKafka, RabbitMQ, and Amazon SQS enable...Read More
1. Orchestration: Think of this as the conductor of an orchestra. It’s all about centralized control and coordination, perfect for managing complex, distributed systems.2. CQRS (Command Query Responsibility Segregation): This one’s a mouthful! It’s about separating how you read data from how you write it. Great for performance optimization.3. Layered (n-tier): The classic approach. It’s...Read More
💡 The SOLID Principles Explained The acronym stands for the following principles: S – Single Responsibility Principle (SRP) A class should have only one reason to change. In practice, this means a class (or module/function) should have only one job or responsibility. If a class handles multiple, unrelated concerns (like calculating payroll and managing database...Read More
The Strangler Fig pattern, often just called the Strangler Pattern, is a design pattern used in software development to incrementally refactor a monolithic application into microservices or a more modular architecture. It’s particularly useful when dealing with large, complex, and business-critical legacy systems where a complete rewrite is too risky or impractical. The name comes...Read More
Have you ever been frequently assigned tasks by various people, and been sought out often for your expertise on a particular topic? That’s an example of informal authority. Informal authority is often forgotten or overlooked in the tech industry, yet it’s a precious resource that significantly contributes to the success of many projects. The ability...Read More
A nice post from Google: https://testing.googleblog.com/2023/11/write-clean-code-to-reduce-cognitive.html How Cognitive Load Works Cognitive load refers to the total amount of mental effort being used in the working memory at a given time. Working memory is the part of our brain responsible for holding and manipulating information needed for complex tasks like learning, reasoning, and problem-solving. It has...Read More
Example 1: Excessive Use of Single Responsibility Principle (SRP) Description Applying the Single Responsibility Principle too strictly can lead to classes and methods that do very little, resulting in an overwhelming number of classes and overly fragmented code. Code Example <?php // Over-engineered example with too many small classes. class UserValidator { public function validateEmail(string...Read More
Symptom 1: Lack of Clarity and Direction It’s shown when the team doesn’t know from where to start and they’re not sure if it’ll work well. Root Cause: When a team is unsure where to start implementing a new feature, it often signals a lack of clear architectural design and modularization. This can be due...Read More
Understanding the Problem: In my previous role, the team faced the challenge of adding new parameters to existing log classes. This issue often arises due to a lack of clear structure, flexibility, and maintainability in the logging system. Applying Domain-Driven Design (DDD): DDD can provide a structured approach to address this problem by: Defining the...Read More
