Case 01 — Streaming
High-volume Kafka consumer tuning
ProblemThe public-safety information system needed to consume high-volume Kafka streams while meeting near-real-time requirements.
ActionOptimized the consumer-side processing path so incoming data is handled promptly instead of backing up under load.
ResultSystem meets its near-real-time data-handling requirement.
Case 02 — Distributed Systems
gRPC multi-source data sync
ProblemData needed to stay consistent across multiple sources spread across several services.
ActionBuilt the synchronization path between services using gRPC.
ResultServices stay in sync on shared data without slower, less structured integration.
Case 03 — Search & Real-time
ElasticSearch + Kafka/Protobuf updates
ProblemThe incident management platform needed full-text search over case records, plus real-time propagation of updates.
ActionBuilt the ElasticSearch search layer and streamed case updates via Kafka with Protobuf as the message format.
ResultCase records became fully searchable; dependent services receive updates in real time instead of batch sync.
Case 04 — Architecture
AOP-based domain restructuring
ProblemThe codebase needed to support an eventual split into independent microservices, without a full rewrite later.
ActionReorganized the codebase by business domain using AOP to separate cross-cutting concerns from domain logic.
ResultModules are structured so they can later split into independent microservices without a rewrite.
Case 05 — Data Modeling
Standalone information-collection module
ProblemA dedicated form module needed its update history queryable quickly, while still feeding other services the essential data they depended on.
ActionStored update history in MongoDB for faster queries, and streamed the essential data onward to other services via Kafka.
ResultA standalone module that stays fast to query locally while keeping downstream services up to date.
Case 06 — Automation
Document auto-fill service (Aspose)
ProblemOfficial reports, decisions and forms were being filled in manually from Word/Excel templates.
ActionBuilt a standalone document service using Aspose that auto-fills these templates from system data.
ResultManual entry on official paperwork was replaced by an automated service.
Case 07 — Reporting
Dashboards & large-scale data export
ProblemManagement needed statistical dashboards and bulk Excel/Word exports over large, multi-source datasets — without the queries behind them becoming sluggish.
ActionBuilt the dashboards and the export pipeline, optimizing the underlying queries to keep them responsive at that volume.
ResultDashboards and large result-set exports stay responsive for analysis and management use.
Personal Project
Forum Student UTE
ProblemStudents and lecturers at the university had no shared place to ask questions and share documents.
ActionBuilt a student/lecturer Q&A and document-sharing forum end-to-end, alone, with Spring Boot, React and PostgreSQL.
ResultA working forum covering both Q&A threads and document sharing in one place.