Repositories

What to take in consideration when building an application

Aspects:

Source code

SOLID Principles: Modular, scalable and maintainable code
- S - Single-responsibility Principle - A class should have only one reason to change
- O - Open-closed Principle - Entities should be open for extension but closed for modification
- L - Liskov Substitution Principle - Subtypes must be substitutable for their base types
- I - Interface Segregation Principle - A class should not be forced to implement interfaces it does not use
- D - Dependency Inversion Principle - High-level modules should not depend on low-level modules. Both should depend on abstractions
DRY (Don't Repeat Yourself): Avoid duplication by abstracting reusable logic
KISS (Keep It Simple, Stupid): Write simple, easy-to-understand code
YAGNI (You Ain’t Gonna Need It): Avoid premature optimizations and unnecessary features
APO (Avoid Premature Optimisations): First, make it work. Then, make it right. Then, make it fast
KFS (Keep Functions Small): Each function should do one thing and do it well
FF (Fail Fast): Detect and handle errors as early as possible

Other:

Logging - Recording events, messages, or errors, critical for debugging, monitoring, and auditing
Tracing - Tracking the flow of requests through distributed systems
Profiling – Capturing CPU/memory usage patterns in real time
Metrics - Quantifiable data points about system health and performance
Alerting – Setting up notifications for anomalies or predefined thresholds
Visualization & Dashboards – Aggregating and presenting observability data