Yaya kake gina microservices da Spring Boot: config, discovery, resilience?

Question

IT Interview Practice · Accepted Answer

Spring Boot tare da Spring Cloud suna ba ka ginshiƙan gine-gine don microservices. Matsaloli guda uku da kowane tsarin rarrabe dole ya warware su ne **centralized configuration**, **service discovery**, da **resilience** a kan gazawar ɓangare. ## Sassan da ke motsi ```text ┌── Config Server (git-backed properties) │ Client ──▶ API Gateway ──▶ Service A ──▶ Service B │ │ │ └──▶ Discovery (Eureka / K8s DNS) ◀── register + look up ``` - **Config Server** yana bauta properties na kowane sabis daga central git repo, don haka kana canza config ba tare da sake tura ba. Ayyuka suna janyo shi a farawa (kuma suna refresh ta `/actuator/refresh`). - **Service discovery** (Eureka, Consul, ko Kubernetes DNS) yana barin Service A ya sami Service B ta *suna* maimakon host da aka sa da hannu, don haka misalai za su iya sikeli da motsi cikin walwala. - **API Gateway** (Spring Cloud Gateway) shi ne mashigin shiga guda ɗaya don routing, auth, da rate limiting. ## Resilience — ɓangaren da juniors ke tsallake A tsarin rarrabe kowane kiran hanyar sadarwa *zai* gaza a ƙarshe. Yi amfani da Resilience4j don hana sabis guda mai sannu ya bazu zuwa katsewa: ```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** yana bugewa a buɗe bayan gazawa da aka maimaita, don haka kiraye-kiraye suna gaza da sauri maimakon tarawa suna jira kan dependency da ya mutu. ## Me ya sa yake da muhimmanci Hira ta senior tana bincika balagar tsarin rarrabe. Ambaton discovery da config shi ne mafi ƙanƙanci; bambanci shi ne yin magana game da **gazawa**: circuit breakers, timeouts, idempotency, da observability (distributed tracing da Micrometer/Zipkin). Ƙwararrun ƴan takara suna kuma tunkuɗewa — suna lura cewa microservices suna ƙara tsadar aiki kuma monolith galibi shi ne zaɓi mai kyau har sai sikeli ya buƙaci in ba haka ba.

Sassan da ke motsi

Resilience — ɓangaren da juniors ke tsallake

Me ya sa yake da muhimmanci

Tambayoyi masu alaƙa