Obumneme @DevOpsWithObum

Thought EBS was just “extra storage”… until I used it. Created an EBS volume, attached it to an EC2 instance, and manually partitioned it. That’s when it clicked: Cloud storage still requires real Linux knowledge. Volumes, partitions, filesystems, nothing abstract about it. DevOps = cloud + fundamentals. #DevOps #AWS #EBS #Linux #LearningInPublic

keyboard_arrow_left Previous keyboard_arrow_right Next

@fromcodetocloud EC2

@irachoudhry thank you, I am enjoying cloud EC2 now

Started working with AWS EC2 today. Spun up instances, connected via SSH, and got a feel for managing servers in the cloud instead of local VMs. Same Linux. Different environment. Much more power. Feels like a step closer to real-world infrastructure. #DevOps #AWS #EC2 #Cloud

keyboard_arrow_left Previous keyboard_arrow_right Next

Built a small SSH lab today. 4 VMs: • 1 scriptbox • 3 remote servers From the scriptbox I practiced: Remote SSH connections Secure file transfers Executing scripts on other machines One machine controlling many. Now I see how tools like Ansible work under the hood. #DevOps

keyboard_arrow_left Previous keyboard_arrow_right Next

Today I learned something small… but powerful. Environment variables in Linux can be exported: • System-wide → /etc/profile • Per-user → ~/.bashrc Same export command. Very different scope. That’s when it clicked: DevOps isn’t just running commands. It’s understanding where configuration lives. Scope matters. Have you ever debugged an issue that was just an environment variable problem? #Linux #Bash #DevOps #LearningInPublic

I started learning Bash scripting today. And I realized something: If you can’t automate it… You don’t really understand it. Writing simple scripts forced me to think about: • Exit codes • Variables • Loops • Conditionals • Permissions DevOps isn’t about tools. It’s about reducing manual work. What’s one Bash command you use daily but never automated? #DevOps #Linux #Bash #LearningInPublic

I used to think Docker was just “run my app in a container.” Today I built a multi-container setup for an e-commerce app… and realized something: Containers aren’t about packaging. They’re about separation of responsibility. Frontend. Backend. Nginx. Each isolated. Each replaceable. That’s when DevOps started to click. Question: At what point did Docker stop being “cool tech” and start making architectural sense for you? #DevOps #Docker #LearningInPublic

keyboard_arrow_left Previous keyboard_arrow_right Next

Agreed. Microservices don’t magically make systems scale good architecture does. What they really optimize for is team autonomy, independent deployments, and reduced coordination overhead. A 3-engineer team can move faster with a well-structured monolith. Microservices start making sense when team boundaries become the bottleneck. Appreciate the perspective.

Saeed Anwar @saen_dev

5 months ago

Microservices are for organizational scale, not technical scale. If you have 3 engineers, a monolith is faster. Microservices become necessary when teams step on each other's toes, not when you hit 10k users. We stayed monolith until we had 5 separate teams.

0 0 2 32 0

As I’m learning more about microservices and DevOps, one thing has become very clear: Architecture is not about trends. It’s about timing. 🚨 Unpopular Opinion: Most startups DON’T need microservices. They need focus. Everyone wants: • Kubernetes • 12 microservices • Service mesh • Fancy DevOps stack But they don’t even have product-market fit. Here’s the reality 👇 Monolith: ✔ Faster to build ✔ Easier to debug ✔ Cheaper to maintain ✔ Perfect for early-stage products Microservices: ✔ Powerful at scale ❌ Operational complexity ❌ Requires strong DevOps ❌ Harder debugging ❌ More moving parts = more failure points Microservices without: • Docker • CI/CD • Monitoring • Logging • Orchestration …is just distributed confusion. Build monolith first. Prove the product. Then evolve when the pain demands it. Architecture is a business decision — not a flex. #DevOps #Docker #Startup #SoftwareEngineering

keyboard_arrow_left Previous keyboard_arrow_right Next

A new month, deeper into my DevOps journey. Over the past weeks, I’ve been building foundations revisiting Linux, understanding networking, working with VMs, containers, and getting hands-on with tools that power modern infrastructure. Welcome to February. 💻🔥 #DevOps

Started getting hands-on with Docker 🐳 Docker solves a real problem: 👉 “It works on my machine” With containers, the app + dependencies are packaged together, so it runs the same everywhere dev, test, prod. No full OS per app. Fast startup. Consistent environments. #Docker

Learning about containers Both solve different problems. Good engineers know when to use which. #devops

TCP is connection-oriented, reliable, and ordered. UDP is connectionless, fast, and best-effort. Use TCP when delivery matters (HTTP, HTTPS, SSH). Use UDP when speed matters (DNS, streaming, monitoring). Right tool. Right trade-off. UDP in one sentence 😭👇 #DevOps #Networking

Learning networking fundamentals: switches vs routers. Switches connect devices within the same network using MAC addresses.(OSI layer 2) Routers connect different networks using IP addresses and handle traffic between them. (OSI layer 3) #DevOps #Networking

@fromcodetocloud well explained

About a month ago, I started learning DevOps. Even with prior Linux experience, I went back to the fundamentals — services, processes, networking, and system design. No shortcuts. DevOps feels good. I still have more work to do. More to build. #DevOps #Linux #LearningInPublic

Completed my first full project setup using a manual multiVM architecture. Stack included: Nginx (entry point) Tomcat (app layer) MySQL (database) Memcached (caching) RabbitMQ (messaging) Manual setup first to understand dependencies, networking, and service interactions #DevOps

keyboard_arrow_left Previous keyboard_arrow_right Next

Today we started project setup using a multi-VM architecture. Manually setting up the stack to understand every moving part: MySQL (DB) Memcached RabbitMQ Tomcat Nginx Rule of automation applies: if you can’t do it manually, don’t automate it. #DevOps #Linux #SystemDesign

keyboard_arrow_left Previous keyboard_arrow_right Next

@CodeRecce JSON and XML/XSD are strict by design, agreed. The comparison was about operational usability, not strictness.

Learned the difference between JSON vs YAML today. JSON → strict, machine-friendly, great for APIs YAML → human-friendly, cleaner syntax, widely used in DevOps configs That’s why tools like Kubernetes, Ansible, and CI/CD pipelines prefer YAML. #DevOps #YAML #JSON #Linux

keyboard_arrow_left Previous keyboard_arrow_right Next