One Ecosystem • Multiple Domains • Continuous Learning
Central hub for my engineering repositories, learning roadmap, and long-term engineering knowledge ecosystem.
This repository serves as the entry point to a collection of production-focused engineering repositories covering operating systems, backend engineering, software architecture, cloud infrastructure, DevOps, platform engineering, and AI engineering.
Technical content lives in the individual repositories.
This repository provides:
- Ecosystem overview
- Repository navigation
- Learning roadmap
- Governance standards
- Repository ownership boundaries
- Long-term direction
Build a production-focused engineering ecosystem that helps engineers understand how modern software systems are designed, built, deployed, operated, scaled, secured, and maintained.
The objective is not collecting notes.
The objective is building a connected engineering knowledge system that explains:
- How systems work
- Why technologies exist
- How components interact
- What breaks in production
- How engineers troubleshoot failures
- How systems evolve over time
The ecosystem connects specialized engineering repositories with practical implementation projects.
The ecosystem is organized around a central portfolio repository that connects engineering knowledge, domain-focused repositories, and practical implementation projects.
Engineering Knowledge
↓
Domain Repositories
↓
Production-Focused Projects
Each repository has a clear ownership boundary and demonstrates a specific engineering capability.
engineering-ecosystem
│
├── operating-system-networking-security
├── backend-engineering
├── software-architecture-system-design
├── cloud-infrastructure-platform
├── devops-release-quality-engineering
├── platform-engineering-playbook
├── ai-engineering
└── engineering-lab
| Repository | Focus Area | Primary Topics |
|---|---|---|
| operating-system-networking-security | Systems Foundation | Linux, Operating Systems, Networking, Security |
| backend-engineering | Application Engineering | Java, Spring Boot, APIs, Databases, Messaging |
| software-architecture-system-design | Architecture & Design | HLD, LLD, Scalability, Design Patterns |
| cloud-infrastructure-platform | Infrastructure Engineering | Cloud, Kubernetes, Terraform, Observability |
| devops-release-quality-engineering | Delivery Engineering | CI/CD, Testing, Release Engineering |
| platform-engineering-playbook | Platform Engineering | Internal Platforms, Developer Experience, IDP |
| ai-engineering | AI Engineering | Agents, MCP, A2A, LLM Engineering |
| engineering-lab | Practical Engineering Projects | Backend services, applications, infrastructure, experiments |
Repositories that establish core engineering knowledge.
- operating-system-networking-security
- backend-engineering
- software-architecture-system-design
Repositories focused on building and operating production systems.
- cloud-infrastructure-platform
- devops-release-quality-engineering
- platform-engineering-playbook
Repositories focused on modern AI systems and agent platforms.
- ai-engineering
Repositories focused on practical implementation and production-style projects.
- engineering-lab
Each repository owns its primary domain.
Topics should have a single source of truth.
Cross-repository duplication should be avoided whenever possible.
Repositories may reference concepts from other repositories, but ownership remains with the designated repository.
| Topic | Repository Owner |
|---|---|
| Linux | operating-system-networking-security |
| Kubernetes | cloud-infrastructure-platform |
| System Design | software-architecture-system-design |
| Platform Engineering | platform-engineering-playbook |
| CI/CD | devops-release-quality-engineering |
| AI Agents | ai-engineering |
- Operating System Networking Security
- Backend Engineering
- Software Architecture System Design
- Cloud Infrastructure Platform
- DevOps Release Quality Engineering
- Platform Engineering Playbook
- AI Engineering Agents Platform
The ecosystem continues to evolve while maintaining clear ownership boundaries and consistent repository standards.
Future expansion areas may include:
- IoT Engineering
- Edge Computing
- Distributed Systems Research
- Production Scenario Libraries
- Engineering Case Studies
- Ecosystem Architecture Diagrams
Future additions should align with the overall engineering ecosystem and maintain clear ownership boundaries.
- Production-focused learning
- Engineering-first thinking
- Practical over theoretical
- Long-term maintainability
- Clear ownership boundaries
- Consistent repository standards
- Human-readable documentation
- Interview and production relevance
The ecosystem should remain a long-term engineering knowledge system rather than a collection of disconnected notes.
Repository-wide standards, governance rules, roadmap planning, and ecosystem decisions are maintained in:
- GOVERNANCE.md
- ROADMAP.md
- CHANGELOG.md