Custom development · open source Java & Go

Services that run on their own, and may fail on their own.

Cut along domain lines, with clean contracts, independently deployable. Quarkus and Go provide the runtime, gRPC and OpenAPI the contracts, without a single commercial component.

WHY THE CUT MATTERS MORE THAN THE COUNT

Microservices are a means, not a goal. Cut wrongly, a monolith becomes a distributed system with the same dependencies, only slower. We cut along the domain, not along technology, and build only as many services as your team can operate.

How we proceed

1

Find the boundaries

Which parts change together, which independently. That determines the cuts, not an org chart and not a target architecture on a slide.

2

Contracts first

OpenAPI for synchronous calls, Avro or Protobuf for events. The contract comes before the implementation so teams can work in parallel.

3

Choose the communication

REST where it suffices, gRPC where performance counts, Kafka where decoupling counts. Every choice with a reason, not out of habit.

4

Build in operations

Health checks, retries, circuit breakers and distributed tracing from day one. A service without observability is a blind spot in production.

WHAT THIS ACTUALLY DELIVERS
Individual

deployable: one fault does not take everything down, one release does not block the whole house.

Open

standards: gRPC, OpenAPI and Kafka are protocols, not products, no lock-in.

As many

services as needed, as few as possible. Operability before architectural aesthetics.

Technologies

All open source, no licence costs, no lock-in.

QuarkusGogRPCOpenAPIApache KafkaEnvoyApache APISIXKubernetes

Related

UW
YOUR DIRECT CONTACT
Uwe Winnwa
Sales · cloud37 AG

30-min intro call, free.
No standard pitch. I listen, ask the right questions and give an honest assessment, even if we are not the right partner.