Hi there! š
I'm Nirav Modi, a Java Spring Boot AWS developer passionate about building awesome web applications.
Interest
š± I would like to learn new technology and Iām currently learning and growing in the world of AWS, Spring Boot.
I will always keep the below points in my subconscious mind
ā Expert Areas where I can rock š and guide someone for best practices ā
- ā Java (13 years)
- ā Spring/Spring Boot (9 years)
- ā Kafka (3 years)
- ā Kubernetes
- ā Flink (3 years)
- ā Docker (5 years)
- ā AWS (5 years)
- ā Serverless Architecture(3 years)
- ā Devops (4 years)
- ā Terraform (2 years)
- ā MQTT (3 years)
- ā Microservices (5 years)
šššØš®š šš«šš”š¢šššš šš±š©šš«š¢šš§šš
I have developed multiple microservices and created event-driven architecture from scratch and the diagram is already attached here where I have used the spring cloud stack and applications always provide
- ā High Availability
- ā High Concurrency
- ā High Visibility
- ā Everything must be in the code base. Every configuration must be in the codebase. It may be a database script or configuration.
- ā Hassle-free release cycle (One-click release without service interruption) due to event-driven architecture
- ā Microservice Architecture
- ā Normalized database design
- ā One database with multiple schema design
Backend:
I have developed multiple microservices using the below technology stack
- āļø Java
- āļø Spring boot Microservices Architecture
- āļø Spring boot ZUUL gateway
- āļø Spring JWT Token-based Security
- āļø Eureka registry server
- āļø Spring cloud-config
- āļø Spring Data JPA
- āļø Event-driven Architecture
- āļø Hazelcast Spring caching
- āļø Hazelcast 2nd level caching
- āļø Kafka (For event-driven and to manage back pressure)
- āļø MQTT
- āļø Normalized database design
- āļø One database with multiple schema design due to microservices architecture
- āļø High Availability
- āļø High Concurrency
- āļø Zero configuration on the release cycle. Every configuration must be in the codebase.
- āļø Hassle-free release cycle (One-click release without service interruption)
DevOps
I have provided a full-proof DevOps solution where Zero downtime while releasing product features. I have implemented a one-click release process using AWS CI/CD and bitbucket hooks.
- āļø Aws Code deploy/ Code pipeline (Integrated bitbucket for hassle-free one-click deployment)
- āļø Dockerization of Java microservices (Build once and run everywhere)
- āļø Kubernetes
- āļø helm chart
- āļø AWS EC2
- āļø API Gateway
- āļø AWS CI/CD Code build/pipeline
- āļø AWS lambda (Automated deployment using lambda)
- āļø ECS Fargate (Deployed all microservices)
- āļø AWS S3
- āļø AWS SQS, SNS
- āļø AWS SFTP
- āļø EKS (Deployed haproxy, Nginx, cratedb, Kafka, Flink, zookeeper, MQTT broker)
- āļø Lambda
- āļø CloudMap
- āļø CloudWatch
- āļø Grafana Dashboard
- āļø Prometheus Metrics
- āļø Kafka
- āļø MQTT
- āļø Terraform
- āļø Cloudformation
Flink
I deployed the below components in the Kubernetes cluster.
- āļø Zookeeper
- āļø Kafka
- āļø Job manager
- āļø task manager
- āļø Flink jobs
About Flink work,
I have developed a "Volume/TIme Wifi Quota Management system" using Flink where I need to continiously calculate user's internet quota. where access point continiously send events to cloud controller and controller will pass events to Flink. For more details about this project you can find in my portfolio.
Using Flink
- I had developed session gap window
- I had used it's queryable functionality to check current state of user's quota
- I had used Flink's core process function and implemented own session gap window due to limitation of flink.
- Used Flink's accumulator and many more things
Kafka
- āļø Kafka docker deployment
- āļø Kafka Kubernetes deployment
- āļø Kafka Helm deployment
- āļø Spring boot integration
MQTT
- āļø End to end certificate-based encryption
- āļø MQTT broker webhook development
- āļø MQTT broker management
- āļø MQTT topic shared subscription
- āļø MQTT proxy listener
- āļø MQTT broker autoscaling on Kubernetes
- āļø MQTT Cluster
IOT
- āļø IOT implementation based on MQTT protocol
- āļø IOT device management, Firmware/OTA management
- āļø IOT device certificate-based security, certificate management
Monitoring Tools
- āļø Prometheus
- āļø Grafana
Let's connect! You can find me on LinkedIn and Stackoverflow.
Feel free to explore my repositories and reach out for collaboration!
Have a great day! š