Unajengaje microservices kwa Spring Boot: config, discovery, resilience?

Question

IT Interview Practice · Accepted Answer

Spring Boot pamoja na Spring Cloud hukupa vipengele vya ujenzi kwa microservices. Matatizo matatu ambayo kila mfumo uliosambazwa lazima uyatatue ni **configuration ya kati (centralized)**, **service discovery**, na **resilience** dhidi ya kushindwa kwa sehemu. ## Vipande vinavyosonga ```text ┌── Config Server (git-backed properties) │ Client ──▶ API Gateway ──▶ Service A ──▶ Service B │ │ │ └──▶ Discovery (Eureka / K8s DNS) ◀── register + look up ``` - **Config Server** huhudumia properties za kila service kutoka git repo ya kati, hivyo unabadilisha config bila kutuma upya (redeploy). Services huipakua wakati wa kuanza (na kujiweka mpya kupitia `/actuator/refresh`). - **Service discovery** (Eureka, Consul, au Kubernetes DNS) huruhusu Service A kupata Service B kwa *jina* badala ya host iliyowekwa moja kwa moja, hivyo instances zinaweza kupanuka na kuhama kwa uhuru. - **API Gateway** (Spring Cloud Gateway) ni lango moja la kuingia kwa routing, auth, na rate limiting. ## Resilience — sehemu ambayo juniors huiruka Katika mfumo uliosambazwa kila mwito wa mtandao *utashindwa* hatimaye. Tumia Resilience4j kuzuia service moja polepole isisababishe mkasa wa kupindukia (cascading outage): ```java @CircuitBreaker(name = "inventory", fallbackMethod = "cachedStock") @Retry(name = "inventory") // retry transient blips @TimeLimiter(name = "inventory") // cap the wait public CompletableFuture stock(String sku) { return inventoryClient.get(sku); // remote call } // Called when the circuit is open or the call fails — degrade gracefully. public CompletableFuture cachedStock(String sku, Throwable ex) { return CompletableFuture.completedFuture(Stock.unknown(sku)); } ``` **Circuit breaker** hufunguka baada ya kushindwa mara kwa mara, hivyo miito hushindwa haraka badala ya kurundikana kwenye threads zikisubiri dependency iliyokufa. ## Kwa nini ni muhimu Mahojiano ya senior huchunguza ukomavu wa mifumo iliyosambazwa. Kutaja discovery na config ni jambo la lazima la msingi; kinachotofautisha ni kuzungumzia **kushindwa**: circuit breakers, timeouts, idempotency, na observability (distributed tracing kwa Micrometer/Zipkin). Wagombea imara pia hupinga — wakibaini kuwa microservices huongeza gharama ya uendeshaji na monolith mara nyingi ni chaguo sahihi hadi kiwango kinapohitaji vinginevyo.

Vipande vinavyosonga

Resilience — sehemu ambayo juniors huiruka

Kwa nini ni muhimu

Maswali yanayohusiana