Sarika | Future DevOps Engineer
735 posts

Sarika | Future DevOps Engineer
@devopsbysarika
👩💻 Self-taught tech explorer in DevOps 🚀 | Building in public | #DevOpsJourney https://t.co/jtRfNXTEwa
शामिल हुए Haziran 2023
48 फ़ॉलोइंग155 फ़ॉलोवर्स

@aditiitwt Main free samajh ke use karti rahi aur yeh millionaire ban gaye😂
हिन्दी

@Just_Raghvi bhn banane ka tareeka thoda casual hai 🤣
हिन्दी

@fromcodetocloud We are not cooked…we are automated
English

AI after slaughtering QA, Devs, and Security in silence:
We are cooked!

Ayaan 🐧@twtayaan
DevOps engineers after AWS DevOps Agent announcement
English

@devopscube without kube-state-metrics, you're just guessing
with it , you're actually observing
English

Kubernetes monitoring without kube-state-metrics is incomplete.
Prometheus scrapes metrics your apps expose. But it does not know:
- How many pods are crashlooping
- Whether your deployment rollout succeeded
- Whats the status of your deployments
That is what kube-state-metrics gives you.
It collects the state of your Kubernetes objects from the k8s API Server and gives them as Prometheus metrics.
If you are using Prometheus Operator, kube-state-metrics comes built in.
We have created a detailed setup guide covering every configuration.
𝗗𝗲𝘁𝗮𝗶𝗹𝗲𝗱 𝗚𝘂𝗶𝗱𝗲: devopscube.com/setup-promethe…
Are you relying only on resource metrics, or also tracking cluster state?
#Kubernetes #DevOps #Observability

English

@devops_nk It’s interesting how expectations evolve with AI as speed increases
English

Honestly, this is the most accurate diagram I've seen.
Waterfall: You plan for 18 months and deliver exactly what nobody needs anymore.
Agile: You deliver something usable at every step, but the CEO keeps asking, "Where's the car?"
AI: You get the car on day one. It has six wheels, the doors are on backwards, and it has a rocket launcher. You spend more time making it yours than actually "building"; it's shaping. owning. verifying. That's what the best AI developers do now. They don't build. They shape and own.

English

@devops_nk @fromcodetocloud I experienced something same . In the first round, I didn’t expect it, but I received a call for the next round. After the interview, I was quite confident that I would clear that round, but then I received a ‘regret to inform you’ email🙂
English

@fromcodetocloud Oh okay bro,
I called to take feedback because the interview went very well, but it looks like nothing is in our hands.
English

Most beginners try to learn 200 AWS services.
You don’t need that.
I spent 30 days focusing only on what truly matters EC2, IAM, S3, and real deployment basics.
check out link👇now published in AWS in Plain English
medium.com/aws-in-plain-e…
English

I just published How to Handle API Errors Like a Pro (Complete Developer Guide) medium.com/p/how-to-handl…
English

I just published How Authentication APIs Work (JWT-Based) A Real-World Guide for Developers medium.com/p/how-authenti…
English

🎟️ Just got my Apertre 3.0 ticket 🎫🔥
Open Source • GitHub • Swags • ₹50K+ rewards
👉 Register now: apertre.resourcio.in
#Apertre3 #OpenSourceIndia #BuildInPublic #DevCommunity #Resourcio #Apertre apertre.resourcio.in/ticket?name=sa…
English

@fromcodetocloud and how would you measure and confirm that latency is actually the problem and not backend processing time ?
English

Your application loads in 80 ms in Australia but takes 600 ms in India.
The backend code, database, and server logic are the same.
How would you fix this?
Answer:
The problem is distance, not code.
Users in India are far from the server, so network latency is high.
To fix it, I would:
1. Use a CDN to serve static content from locations closer to users
2. Deploy backend services in multiple regions or move them closer to India
3. Enable caching at the edge for APIs where possible
4. Optimize network routing and reduce unnecessary round trips
The goal is to bring the data closer to the user, not rewrite the application.
English












