👨‍🔧
The Ops Compendium
  • The Ops Compendium
  • Definitions
    • Ops Definition Comparisons
  • ML & DL Compendium
  • MLOps
    • MLOps Intro
    • MLOps Teams
    • MLOps Literature
    • MLOps Course
    • MLOps Patterns
    • ML Experiment Management
    • ML Model Monitoring & Alerts
    • MLOps Tools
    • MLOps Deployment
    • Feature Stores & Feature Pipelines
    • Model Formats
    • AI As Data
    • MLOps Interview Questions
    • ML Architecture
  • DataOps
    • SQL
    • Tools
    • Databases
    • Database Modeling
    • Data Analytics
    • Data Engineering
    • Data Pipelines
    • Data Strategy
    • Data Vision
    • Data Teams
    • Data Catalogs
    • Data Governance
    • Data Quality
    • Data Observability
    • Data Program Management
    • Data KPIs
    • Data Mesh
    • Data Contract
    • Data Product
    • Data Engineering Questions & Training
    • Data Patterns
    • Data Architecture
    • Data Platforms
    • Data Lineage
  • DevOps
    • DevOps Strategy
    • DevOps Tools
      • Tutorials
      • Continuous Integration
      • Docker
      • Kubernetes
      • Cloud Objects
      • Key Value DB
      • API Gateway
      • Infrastructure As code
      • Logs
      • ELK
      • SLO
    • DevOps Courses
  • DevSecOps
    • Definitions
    • Tools
    • Concepts
  • Architecture
    • Problems
    • Development Concepts
    • System Design
Powered by GitBook
On this page
  • PATTERNS
  • Programming Concepts

Was this helpful?

Edit on GitHub
  1. Architecture

Development Concepts

PreviousProblemsNextSystem Design

Last updated 10 months ago

Was this helpful?

PATTERNS

DovAmir

Programming Concepts

- based on the class should do one thing, so we are letting other classes create 3rd party/class objects for us instead of doing it internally, either by init passing or by injecting in runtime.

- the five principles of object oriented.

Dependency injection
SOLID
SOLID
Software and architectural design patterns