Infrastructure is a supporting skill for me, not the direction I want to be hired for. I understand enough Docker, cloud, queues and hosting to build, run and debug my own systems when a project needs it.
The Story
Why I keep Infrastructure close
Good infrastructure knowledge helps me build software that is easier to run, debug and maintain.
I treat it as practical literacy and hobby lab work: useful for backend, AI and self-hosted projects, but not a DevOps career track.
PracticalEnough operational hygiene to keep my own systems understandable.
CapableComfortable with containers, hosting basics and service wiring.
UsefulFocused on simple setups that support product and backend work.
CarefulSecurity basics, secrets handling and sensible defaults.
Core Capabilities
Containerization literacy
Docker and lightweight k3s setups when a project needs a realistic local or hobby environment.
Messaging basics
RabbitMQ and MQTT where backend, IoT or local experiments need asynchronous communication.
Data & Persistence
PostgreSQL, MongoDB and storage choices from an application developer perspective.
Repeatable setup
Small repeatable setup scripts and config, mostly to avoid manual project drift.
Operational visibility
Basic logs and metrics so local or small hosted systems are not opaque.
What I understand
Cloud fundamentals
Enough to understand compute, storage, networking and IAM tradeoffs.
Self-hosting lab
Small clusters and containers for personal projects or realistic testing.
Automation when useful
Simple scripts and checks that make local workflows repeatable.
Message brokers & IoT communication
RabbitMQ for services, MQTT for device-style communication.
Database operations
Backups, migrations and reliability from an app-owner perspective.
Operational hygiene
Secrets, least privilege and hardening basics, not security theatre.