Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
62 changes: 62 additions & 0 deletions content/experts/nitish-songara.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,62 @@
---
name: 'Nitish Songara'
slug: 'nitish-songara'
title: 'Senior Data Engineer'
bio: 'Senior Data Engineer experienced in building scalable data pipelines, cloud infrastructure, containerized workloads, and automated CI/CD workflows.'
avatar: '/images/experts/nitish-songara.jpg'
specialties:
- Docker
- Kubernetes
- Terraform
- CI/CD
- AWS
- Data Engineering
- Infrastructure as Code
availability: 'Open to consulting and collaboration'
location: 'India'
email: 'nitishsongara75@gmail.com'
website: 'https://github.com/sonu7089'
github: 'https://github.com/sonu7089'
---

## About Me

I am a Senior Data Engineer with over five years of experience designing, automating, and operating cloud-native data platforms and DevOps infrastructure across enterprise and high-growth environments.

## What I Work On

- **Cloud & Data Infrastructure**: Provisioning reliable cloud environments and distributed data processing architectures using Terraform and AWS
- **Containerization & Orchestration**: Packaging and scaling data services and microservices with Docker and Kubernetes
- **CI/CD & Automation**: Building automated testing, deployment, and observability pipelines for data and backend engineering teams
- **Data Engineering at Scale**: Designing fault-tolerant ETL/ELT pipelines, lakehouse architectures, and real-time streaming systems

## My Stack

### CI/CD & Version Control

- **Git & GitHub Actions** for source control, automated testing, and container image build pipelines
- **ArgoCD** for declarative GitOps deployments and continuous reconciliation on Kubernetes

### Infrastructure & Cloud

- **Terraform** for provisioning reproducible cloud and data platform infrastructure as code
- **AWS** for scalable compute, object storage, and managed data services

### Containers & Orchestration

- **Docker** for consistent local development environments and packaging data/backend services
- **Kubernetes** for orchestrating containerized microservices, batch jobs, and distributed workloads

### Monitoring & Observability

- **Prometheus + Grafana** for cluster, pipeline, and application metrics visualization
- **CloudWatch & OpenTelemetry** for centralized logging, tracing, and alerting

### Why This Stack

I chose this combination because treating both infrastructure and data pipelines as declarative code eliminates configuration drift between environments. The biggest win has been pairing GitHub Actions with ArgoCD and Terraform: every infrastructure or pipeline change goes through pull request review and rolls out predictably with a full audit trail in Git.

### One Thing I'd Change

If I were starting fresh on a new platform today, I'd standardize on `ApplicationSet` generators and strict cost-allocation tagging in Terraform from day one rather than retrofitting multi-environment GitOps templates and FinOps visibility after the cluster footprint grows.

Binary file added public/images/experts/nitish-songara.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.