Nitish Kumar

Programmer, Cloud Server Expert, Web Architect, JavaScript, PHP, Python, Entrepreneur, Photographer, Foodie

[Nitish Kumar @tonitishkumar]

@OfficialDMRC Thank you for your response. But at Vaishali metro station they are not providing such options. They are forcefully sending everyone for Airtel Payment Bank card. Airtel has separate counter near security check but if you need token we have to go 2 floor down

[Nitish Kumar @tonitishkumar]

@OfficialDMRC why are you forcing Everyone to open account in airtel payment bank? I just need simple DMRC card but at Vaishali metro station i have been forced to buy Airtel Payment Card.. if it your official your official stand then why not I DMRC stamp or logo on it

[Nitish Kumar @tonitishkumar]

@CIBIL is biggest scam in India. No enquiry, not a single miss emi. Still having CIBIL score get down. No accountability, Can't ask any questions. @FinMinIndia @nsitharaman can you make add little transparency in CIBiL

[Nitish Kumar @tonitishkumar]

@Atulsingh_asan Very true. I also got frustrated with them and closed my @bankofbaroda account at indirapuram. Staff behaviour towards customer is very poor

[Nitish Kumar @tonitishkumar]

I'm frustrated! 😤 @airtelindia @Airtel_Presence, why am I being harassed with 7-8 daily calls about a loan I never requested? 📞 I haven't updated my @airtelbank profile either. People keep promising the calls will stop, but they don't! 😡 #CustomerService

[Rohit @Iam_Rohit_G]

Number of Jobs created by Blinkit : 1,85,000+
Number of Jobs created by Zepto : 1,20,000+
Number of Jobs created by Big Basket :80000+
Number of Jobs created by Zomato : 5,50,000+
Number of Jobs created by Swiggy : 6,90,000
Number of Jobs created by Urban Company : 40000+
Number of Jobs created by OLA : 1 million+
Number of Jobs created by Uber : 1.4 Million+
Number of Jobs created by Rapido : 8,00,000+

No of jobs created by Kunal Kamra : 0
No of Jobs created by Raghav Chadda : 0
No of Jobs created by Ravish Kumar : 0

People who have created 0 jobs are questioning people who have created million of Jobs in India!!

[Nitish Kumar @tonitishkumar]

ॐ पार्वती पतये हर हर महादेव!

[Nitish Kumar @tonitishkumar]

@anandmahindra Why only for daughters. It should be also for Son. Upbringing of Son or daughter having equal responsibility even raising son with manners is more tough.

[Nitish Kumar @tonitishkumar]

@TTechFusionist AWSFix

[Adarsh Gupta ✨ @Adarsh____gupta]

Do this:

1. Open AWS and create an account.

2. Go to EC2, spin up an instance, generate a key pair, and SSH into it from your local system. Just play around install Nginx, deploy a Node app, break things, fix them.

3. Decide to launch something? Go to Security Groups open ports for HTTP (80), HTTPS (443), and SSH (22).

4. Grab your instance’s public IP, open it in your browser, and you’ll see your app running on the cloud.

5. Start scaling ? create another EC2 instance and set up an Application Load Balancer to route traffic.

6. Tired of adding instances manually? Use Auto Scaling Groups (ASG) define min/max instances, attach a launch template/AMI of your app, and AWS will scale automatically based on CPU or request load.

7. Getting millions of requests and your DB is choking? Use Kafka or SQS for buffering high-throughput workloads. Learn more about async

8. Store images, videos, or backups? Use S3 connect it from your app via the SDK, and make a file uploader.

9. Use RDS for managed databases (MySQL/Postgres). AWS handles backups, scaling, and maintenance.

10 Use CloudWatch to monitor your instances, logs, and metrics. Set up alerts when CPU spikes or memory usage is high.

11. For networking, explore VPCs subnets, route tables, gateways. This is where you learn how AWS isolates traffic securely. You will learn really well about networking here. Just create a vpc and play around

12. Once you’re comfortable, try Terraform to automate infra because that's 100X easier to manage state.

Stage 13: Say Fuck AWS for stealing money and buy your own VPS, set up Docker, or use Coolify for one-click PaaS setups.

[Nitish Kumar @tonitishkumar]

@ZubairC44199324 @khurpenchh Apki jaankari adhuri hai. Ye area hospital ke already reserved tha na ki ramleela ground ke liye

[Akhilesh Mishra @livingdevops]

Dear DevOps Engineers, a gentle reminder to:

- Learn Linux fundamentals before Shell scripting
- Learn Shell scripting before Configuration Management
- Learn Networking basics before Cloud Infrastructure
- Learn Virtual Machines before Containers
- Learn Git basics before GitOps
- Learn Containers before Container Orchestration
- Learn Single server deployment before Microservices
- Learn Manual deployments before Automation
- Learn Configuration files before Infrastructure as Code
- Learn Application logs before Observability platforms
- Learn Basic monitoring before Advanced telemetry
- Learn Traditional security before Cloud security
- Learn Local environments before Cloud environments
- Learn System administration before Site Reliability Engineering
- Learn Bash scripting before Python automation
- Learn YAML basics before Kubernetes manifests
- Learn TCP/IP before Service Mesh
- Learn Load balancing before Auto-scaling

It all starts with the core infrastructure & operations fundamentals.
Have the patience to master the basics before diving into advanced tooling and automation.

Strong foundational knowledge helps you understand WHY things work the way they do, not just HOW to use them.

This enables you to troubleshoot effectively and adapt to new technologies as they emerge.

What would you add to the list?

[Akhilesh Mishra @livingdevops]

Most candidates can explain Docker basics in Devops/SRE interviews but freeze when asked about real-world disasters.

Here are 10 questions that reveal who’s actually fought production fires vs who’s just watched YouTube videos:

👉 You deploy on Friday afternoon and traffic drops 30% with no error alerts. Your CEO is asking questions. What’s your investigation process?

👉 Design a backup strategy for a distributed database that processes 50TB daily while maintaining ACID compliance across regions

👉 Your entire CI/CD pipeline was compromised and malicious code reached production. Walk through your containment and recovery plan

👉 Implement a deployment freeze process that can halt 200+ simultaneous deployments across teams within 60 seconds

👉 Design a resource allocation strategy where dev environments cost 80% less than production but maintain realistic testing conditions

👉 Your observability costs are 40% of your infrastructure budget. How do you optimize without losing critical visibility?

👉 Create a disaster recovery test that validates your 4-hour RTO without impacting live traffic or customer data

👉 Design a multi-tenant Kubernetes architecture where one tenant’s resource spike can’t impact others

👉 Your database replica lag hits 10 minutes during peak hours. How do you solve this without affecting write performance?

👉 Implement automated compliance scanning that prevents policy violations while maintaining developer velocity

Real DevOps isn’t about memorizing kubectl commands.

It’s about making impossible decisions under pressure with incomplete information.

How many of these have you actually faced in production?

[Akhilesh Mishra @livingdevops]

Dear DevOps Engineers,

If your infra supports 10 users
→ a single EC2 box and manual deploys will do
If you’re handling 10M requests a day
→ you’d better be thinking load balancers, ASGs and rate limiting
—
If one team pushes code once a week
→ shell scripts and manual approvals might work
If 20 engineers ship daily
→ invest in CI/CD, pipelines, rollback strategies and policy gates
—
If downtime breaks a low-traffic page
→ a status page and “we’re working on it” is fine
If downtime nukes revenue flows
→ HA, health checks, circuit breakers and multi-AZs are mandatory
—
If you're consuming infra
→ basic terraform apply is enough
If you're building platforms
→ modules, state backends, drift detection, and policy as code are your baseline
—
If all logs fit on your screen
→ grep and tail are fine
If you support dozens of microservices
→ structured logs, traces, alerting, and dashboards are non-negotiable
—
If your infra fits in your head
→ docs are a nice-to-have
If it spans regions and teams
→ diagrams, runbooks, onboarding guides, and chaos drills are survival
—
If only you touch prod
→ naming things poorly is annoying
If a team maintains prod
→ bad names are costly traps with pager duty consequences
—
If you're debugging once a month
→ SSH works
If you're on-call every week
→ automate, alert smart, and reduce your MTTR with observability
—
If it’s a sandbox
→ YOLO your infra, learn by doing
If it’s production
→ version control, review gates, secrets management and audits are the floor
—
If it's a weekend hack
→ skip the Terraform, go fast
If it's a regulated industry
→ compliance, encryption, logging, IAM boundaries and rollback are table stakes
—
People think DevOps is just about CI/CD and YAML.
It’s really about:
– Knowing when to automate vs. script
– Removing friction without removing control
– Creating systems where engineers can ship without fear

The best DevOps engineers don’t just automate.

They make the system safe for everyone else to move fast without breaking everything.

[Akhilesh Mishra @livingdevops]

- DevOps is dead
- Ai agents will be managing your Kubernetes clusters.
- Infrastructure-as-Code will be fully automated!
- CI/CD pipelines will be built by AI!

I've been hearing these dramatic predictions since ChatGPT launched.

After 2.5 years of actually using AI tools in my daily work, I can tell you this: the reality is very different from the headlines.

Yes, AI can write Terraform code, kubernetes manifest, basic pipelines and scripts people already posted in github, stack overflow.

But try getting it to:
- Debug a complex Kubernetes networking issue
- Handle multi-region failover scenarios
- Design scalable microservices architecture
- Manage security compliance across cloud providers
- Use newly released, cloud services and security implementation.
- Work with cross teams, negotiating, managing conflicts and keep things running.

Even autonomous AI agents fall short:
- They can't maintain context across your entire infrastructure
- Struggle with real-world edge cases
- Can't understand company-specific requirements
- Limited by their training data when facing novel problems

If your job is just copying Terraform templates, copy-pasting code from Stack Overflow you should be concerned.

But if you understand distributed systems, security implications, and complex infrastructure patterns - AI will amplify your capabilities, not replace them.

The winners will be engineers who can:
- Think deeply about systems architecture
- Solve novel infrastructure challenges
- Use AI to automate routine work
- Focus on high-impact engineering decisions

Stop believing the hype. Start focusing on becoming a better engineer who knows how to use AI as another tool in their arsenal.

The future isn't AI replacing DevOps engineers. It's DevOps engineers who understand how to leverage AI efficiently versus those who don't.

[Govardhana Miriyala Kannaiah @govardhana_mk]

AWS (US-EAST-1) DynamoDB Outage report explained in plain English.

1. A race condition in DynamoDB’s DNS automation deleted its main endpoint record.

2. This happened when 2 DNS systems updated Route 53 at the same time and removed all IPs.

3. DynamoDB went offline, and services that depend on it like EC2, Lambda, Redshift, and IAM stopped working.

4. EC2 could not launch new instances because it uses DynamoDB to track server state.

5. Network and Load Balancer systems failed next, causing connection errors across AWS.

6. Engineers fixed the DNS issue, full recovery took about 15 hours.

If you are a DevOps or Cloud Engineer, this is a great use case to understand.

A small DNS automation glitch can bring half the internet down.

56K+ read my DevOps and Cloud newsletter: https://t.co/WBucLdwdsb

What do we cover:
DevOps, Cloud, Kubernetes, IaC, GitOps, MLOps

🔁 Consider a Repost if this is helpful

[Nitish Kumar @tonitishkumar]

@CommonBS786OM Ek Dalit MLA bhi ko bhi Mara gya hai aaj hi. Uspe bolne me sharam aa rahi hai ya paise nahi mile uske liye bolne ke liye?

[Nitish Kumar @tonitishkumar]

@AnilYadavmedia1 Are bhai aaj hi ek ST MLA ko WB me maara gya hai. Kuch bologe nahi ispe? Ya jaat sirf UP MP me ho dikhta hai

[Nitish Kumar @tonitishkumar]

@RailMinIndia @IRCTCofficial this is weird. Unable to book tatkal ticket. On time it's showing "Site currently not available". Once tatkal ticket availability finished, site become available. Anyone will take responsibility? Is Tatkal can buy from agents only?

[Nitish Kumar @tonitishkumar]

@Mahtoji_007 @BJP4India Jharkhand me to @INCIndia govt hai na?