Do we need Kafka?
Not always. We compare broker options, managed services, and in-process patterns against your throughput, ordering, and operational capacity — then document trade-offs you can defend to engineering and finance.
Programming consulting for event-driven software architecture — scoped delivery work and ongoing technical advisory from Kuala Lumpur.

Teams often start with REST chains that look simple on a diagram yet amplify latency, coupling, and retry storms under load. Event-driven boundaries only help when ownership, schema evolution, and delivery semantics are designed together.
We work on the problems that show up after the first Kafka topic ships: duplicate events, poison messages, unclear consumer contracts, and observability that cannot trace a business action across services.

Dual writes between a database and a broker are a common source of silent data loss. Without transactional outbox or an equivalent pattern, “published” events may never match committed state.
Partition keys chosen for throughput can break business ordering. We map which invariants must be sequential versus which can be parallel, then align topic design and idempotent consumers accordingly.
Reliable event pipelines are a design exercise in boundaries — not a broker purchase.

Paid programming consulting is delivered as fixed-scope architecture projects (event catalogues, bounded context maps, delivery semantics reviews) or as ongoing technical advisory when your team needs a steady architectural partner.
Engagements are quoted after a written scope confirmation; starting fees are discussed individually and stated in Malaysian Ringgit when proposed. See how engagements are structured.
Not always. We compare broker options, managed services, and in-process patterns against your throughput, ordering, and operational capacity — then document trade-offs you can defend to engineering and finance.
We define compatibility rules per event type, align producer and consumer contracts, and wire validation into CI so breaking changes are caught before deployment.
Standing architecture reviews, incident postmortems on messaging paths, pairing on consumer design, and backlog grooming for platform work — billed as a monthly advisory block with written summaries.
Describe your current integration pain, target domains, and any brokers or clouds already in use. We reply by email with next steps.