You will get a production Apache Kafka pipeline in Java, deployed on Kubernetes

Pavlo Z.Status: Offline
Pavlo Z.
5.0

Let a pro handle the details

Buy Web Application Programming services from Pavlo, priced and ready to go.
Pavlo Z.Status: Offline
Pavlo Z.
5.0

Let a pro handle the details

Buy Web Application Programming services from Pavlo, priced and ready to go.

Project details

Most teams do not break on their first Kafka topic. They break on the tenth, under real load, when a consumer falls behind or a broker drops. I build Apache Kafka and Kafka Streams pipelines that hold up: clean topic and partition design, sensible delivery semantics, and processing that recovers after a failure. Two recent Upwork engagements, a Kafka Streams pipeline and an Apache Flink PoC, both closed at 5.0 of 5, and I hold an AWS Solutions Architect Associate certification. You get a pipeline your own team can run after I leave, not a black box. Tell me your scale target and I will scope it before you commit.
What's included
Service Tiers Starter
$700
Standard
$1,800
Advanced
$3,500
Delivery Time 7 days 14 days 28 days
Number of Revisions
123
Design Customization
-
-
-
Content Upload
-
-
-
Responsive Design
-
-
-
Source Code
-
-
-
Optional add-ons You can add these on the next page.
Fast Delivery
+$350 - $1,750
Additional Revision
+$150

Frequently asked questions

5.0
2 reviews
100% Complete
1% Complete
(0)
1% Complete
(0)
1% Complete
(0)
1% Complete
(0)

GL

Gary L.
5.00
Jul 19, 2022
Data Transformation and Pipeline using Kafka Streams Pavlo is a great developer to work with. Strong technical skills and communication. Will hire again in the future.

IS

Itamar S.
5.00
Sep 29, 2020
Create an Apache Flink PoC app for a given scenario
Pavlo Z.Status: Offline

About Pavlo

Pavlo Z.Status: Offline
Apache Kafka & Java Engineer | Streaming Data Pipelines | IoT Backend
100% Job Success
5.0  (2 reviews)
Lviv, Ukraine - 2:18 am local time
Looking for an Apache Kafka and Java engineer who can design real-time streaming and data pipelines that hold up under production load? Over the past decade I have built Java backend, Apache Kafka streaming, and data-engineering pipelines across SoftServe, Eleks, and Euristiq, with the last six-plus years centered on Kafka, Kafka Streams, and Apache Flink for platforms that cannot afford to drop a message - including IoT telemetry ingestion at scale.

✅ Apache Kafka and Java engineer, 10 years backend, 6+ years on Kafka and streaming
✅ Two paid Upwork engagements closed at 5.0 of 5 - a Kafka Streams pipeline and an Apache Flink PoC
✅ 100% Job Success Score across 211 tracked hours, AWS Solutions Architect Associate certified
✅ Production Kafka, Kafka Streams, Kafka Connect, and Flink on Kubernetes, plus data-engineering and MQTT IoT ingestion pipelines

━━━━━━━━━━━━━━━━━━━━━━━━

🔷 What I Do as Your Apache Kafka and Java Engineer

I design and build streaming data pipelines and Java backend systems that scale independently of the write path and stay reliable when volume spikes. My work covers Apache Kafka topic and partition strategy, Kafka Streams stateful processing, Kafka Connect integrations, and Apache Flink stream processing, deployed on Kubernetes with monitoring in place.

Whether you need a new Kafka pipeline, a data-engineering or ETL workload, a Spring Boot microservice backend, an event-driven architecture, or a Flink real-time processing layer, I bring production-grade engineering and clean handover to every project.

🔷 Core Apache Kafka and Java Backend Services

▸ Apache Kafka pipeline design - topic and partition strategy, consumer groups, delivery semantics
▸ Kafka Streams stateful processing, Kafka Connect source and sink connectors, schema registry
▸ Apache Flink real-time stream processing and fault-tolerant pipeline architecture
▸ Data engineering, ETL pipelines, and Big Data batch and streaming workloads
▸ MQTT-based IoT ingestion feeding Kafka topics downstream
▸ Java and Kotlin Spring Boot microservices, REST and GraphQL APIs
▸ Event-driven architecture and high-throughput backend services
▸ Elasticsearch search infrastructure downstream of Kafka topics
▸ Kubernetes and Docker deployment on AWS and GCP

🔷 Where I Have Shipped It

At Euristiq, an AWS Advanced Tier partner, I build production data and backend systems for enterprise clients: moving service-to-service messaging onto Apache Kafka, building Kafka and Kubernetes backends for high-load platforms, and standing up MQTT IoT ingestion that feeds Kafka topics downstream. On Upwork, a Kafka Streams data transformation pipeline and an Apache Flink processing PoC both closed at 5.0 of 5 across more than 200 tracked hours, and the Kafka Streams client left a review citing strong technical skills, communication, and a will-hire-again. Earlier roles at Eleks and SoftServe covered Java and Spring Framework backend development, SQL design, and REST API engineering for global software teams.

🔷 Who I Work With

I work best with teams that have a real data problem, not a tutorial one: product companies pushing high event volume, fintech and IoT platforms with hard reliability needs, and engineering teams who already know they need Apache Kafka or Apache Flink and want someone who has run them in production. If your pipeline only needs to move a few rows a day, I am probably overqualified for it.

🔷 My Engineering Process

Send me your architecture and within 24 hours I will tell you whether the approach fits your scale, before any contract is signed. From there: a written design covering Kafka topic and partition strategy, consumer group layout, and delivery semantics; then implementation in Java or Kotlin on Kubernetes with monitoring; then a handover your own team can run. No black-box Kafka pipelines you cannot maintain after I leave.

🛠 Tech Stack

⚡ Apache Kafka, Kafka Streams, Kafka Connect, Apache Flink
⚡ Java, Kotlin, Spring Boot, Spring Framework
⚡ Kubernetes, Docker, AWS, GCP
⚡ Elasticsearch, MongoDB, SQL, GraphQL
⚡ MQTT, schema registry, ETL pipelines

━━━━━━━━━━━━━━━━━━━━━━━━

If you need an Apache Kafka and Java engineer who designs streaming systems that survive real load and hands them over clean, send me a message. Happy to review your current pipeline architecture or jump on a call to scope your project.

Steps for completing your project

After purchasing the project, send requirements so Pavlo can start the project.

Delivery time starts when Pavlo receives requirements from you.

Pavlo works on your project following the steps below.

Revisions may occur after the delivery date.

Discovery and design

I review your architecture and event volume, then write a short design covering topic and partition strategy, delivery semantics, and consumer layout.

Build

I implement the pipeline in Java or Kotlin with tests, Docker packaging, and monitoring hooks, checking in at agreed points.

Review the work, release payment, and leave feedback to Pavlo.