Payments & PCI-DSS • Event-Driven Architecture • High Performance Systems
Software Engineer since 2015, specializing in microservices architecture with focus on resilience, security, performance, and data governance (PCI-DSS compliance). I work extensively with Java 21, Spring Boot, and Eclipse Vert.x, designing scalable systems on AWS (EKS, API Gateway, Cognito, Secrets Manager, Kinesis, RDS), and building event-driven architectures using Kafka, SQS, and RabbitMQ.
- 🔭 Currently: architecting complex payment systems, implementing advanced observability patterns, performance optimization, and data governance strategies with PostgreSQL.
- 🎯 Goals: pursuing architecture certifications and technical leadership roles, expanding multi-cloud expertise (AWS, Azure, GCP).
- 💬 Ask me about: Java/Vert.x, Spring, Kafka, PostgreSQL/SQL Server, CI/CD, AWS Well-Architected, PCI-DSS.
|
Designing high-availability, consistent systems with PCI-DSS compliance. Expert in transactional integrity, idempotency, and financial data security. Implementing circuit-breaker, retry, idempotency patterns. Distributed tracing, business-level metrics, and proactive monitoring strategies. |
Establishing data catalogs, quality rules, naming conventions, audit trails. CDC pipelines (Debezium) to analytical stores like Pinot. Achieving low latency through JVM tuning, A/B profiling, back-pressure handling, IO optimization, and resource-efficient design. |
|
Java 21 • Vert.x • AWS Secure key/secret management service with automated rotation and comprehensive audit trails for PCI-DSS compliance.
|
Debezium • Kafka • PostgreSQL Real-time data replication platform for analytics and fraud detection with eventual consistency guarantees.
|
gRPC • Go • Apache Pinot Low-latency microservice for querying payment metrics and real-time analytics with sub-second response times.
|
💡 Public repositories will be pinned soon • Check back for code samples and implementation details
- CI/CD Pipelines: GitHub Actions with automated linting, testing, SAST/DAST analysis, and container scanning.
- Infrastructure as Code: Terraform/Helm with GitOps workflows across dev/qa/prod environments.
- Documentation: C4 Model + Mermaid/PlantUML diagrams, ADRs (Architecture Decision Records), and release checklists.
All my repositories follow consistent conventions for maintainability and collaboration:
- README.md: Clear project overview, setup instructions, usage examples
- LICENSE: Open-source licensing (typically MIT/Apache 2.0)
- CODE_OF_CONDUCT.md: Community guidelines based on Contributor Covenant
- CONTRIBUTING.md: Contribution workflow, coding standards, PR process
- Repositories:
kebab-case(e.g.,payment-gateway-service) - Branches:
feature/,bugfix/,hotfix/,release/prefixes - Variables/Functions: Follow language idioms (camelCase for Java, snake_case for Python)
- Conventional Commits:
type(scope): description- Types:
feat,fix,docs,refactor,test,chore,perf - Example:
feat(auth): add JWT token refresh mechanism
- Types:
- PR Templates: Checklist-driven with sections for changes, testing, and breaking changes
I'm available for:
- 🎓 Mentorship in architecture and microservices design
- 🔍 Design Reviews for systems and pipelines (security and performance focus)
- 🎤 Tech Talks/Workshops on Java 21, Vert.x, Kafka, AWS, PCI-DSS compliance
