Hi everyone,

I’m a student in the early stages of a DevOps degree, and I have to complete an individual project within 5 months. My lecturer asked for a unique, new topic that is purely DevOps, not system engineering. I searched for a long time without luck, then used Perplexity to explore ideas and found one that my lecturer approved. He told me to start with a literature review and continue from there.

The topic is: I don't want to reveal it here, but I'll let you know when you are willing to help me.

Now that I’m starting, I’m honestly panicking. DevOps is new to me; the degree has only just begun, and many of the tools and terms are unfamiliar. I’m comfortable with practical work, but I’m worried about how much I need to learn in such a short time and whether I can finish on schedule.

I’d really appreciate help with:

1. How should I approach the literature review when I don’t know the terminology yet?
2. What core DevOps concepts and tools should I learn first (CI/CD, containers, IaC, etc.)?
3. Any tips for planning a 5-month project as a beginner?
4. Good free resources, communities, or books you’d recommend?

If you’ve been through something similar, I’d love to hear how you handled it. Thanks so much in advance!

As i always wanted to help and teach people, I wanted to do my part by teaching, by the way I'm working as a devops enginner.

FYI without money , for the first time I'm gonna do what I wanted to , let me know which topic has to be picked and interested people ping the comments.

I want to start the basics on kubernetes cuz I like kubernetes I want to start with this. Thank you. Not sure if this post will be retained or delayed.

honestly i dont get why current multi-agent setups are built like this.

if you connect 4 or 5 mcp servers (github, postgres, filesystem, slack etc) you easily end up with 40-50+ tool schemas. right now the standard pattern in langchain or claude code is dumping all 4,000+ tokens of json schemas into the prompt on every single turn just so the llm can pick which function to run.

you end up paying token costs and waiting ~2 seconds of network latency just for what is basically an L7 routing lookup.

i spent the last few weeks testing if we can just decouple tool discovery completely from the llm using a local cpu vector mesh (all-MiniLM-L6-v2 + chromadb hnsw index) and a split execution daemon.

instead of embedding just the function name (which fails on synonyms), i combined the tool name, description, schema keys, and tags into a single profile vector. when a prompt comes in, it embeds the query on cpu and pulls the top match before ever touching the llm.

ran a cold-cache benchmark across 100,000 synthetic tool endpoints on my local machine (standard cpu, no gpu):

method top-1 acc avg latency p95 latency

---------------------------------------------------------------

naive keyword scan 38.1% 46.41 ms 57.60 ms

bm25 lexical index 40.4% 194.05 ms 247.25 ms

local vector mesh 70.7% 9.56 ms 11.44 ms

in-memory fast path n/a 0.082 ms 0.15 ms

We build a patch management product. Right now it uses Dynatrace to pull health signals from managed assets (things like whether a service or host is healthy before and after a patch is applied).

Before we commit further, I'd like to hear from people who use these tools every day. Which APM or monitoring tool does your team use (Dynatrace, Datadog, New Relic, AppDynamics, Elastic, Grafana/Prometheus, something else)?

I'm most curious about:

- How reliable the health and alerting data is in practice (false positives, gaps, lag)

- How comfortable your team is using it day to day

- How easy it was to integrate with other tools through its API

- Anything you regret or wish you'd known before choosing it

I'm not selling anything. I just want to understand what teams trust so we can support the right tools. Thanks in advance!