Kif tibni microservices bi Spring Boot: config, discovery, resilience?

Question

IT Interview Practice · Accepted Answer

Spring Boot flimkien ma' Spring Cloud jagħtik il-blokki tal-bini għall-microservices. It-tliet problemi li kull sistema distribwita trid issolvi huma l-**konfigurazzjoni ċentralizzata**, is-**service discovery**, u r-**resilience** kontra fallimenti parzjali. ## Il-partijiet li jiċċaqilqu ```text ┌── Config Server (git-backed properties) │ Client ──▶ API Gateway ──▶ Service A ──▶ Service B │ │ │ └──▶ Discovery (Eureka / K8s DNS) ◀── register + look up ``` - **Config Server** iservi l-properties ta' kull servizz minn git repo ċentrali, biex tbiddel il-config mingħajr ma terġa' tiddeployja. Is-servizzi jiġbduha meta jibdew (u jaġġornaw permezz ta' `/actuator/refresh`). - **Service discovery** (Eureka, Consul, jew Kubernetes DNS) iħalli lil Service A isib lil Service B bl-*isem* minflok host hard-coded, biex l-istanzi jkunu jistgħu jiskalaw u jiċċaqilqu liberament. - **API Gateway** (Spring Cloud Gateway) huwa l-uniku punt tad-dħul għar-routing, l-auth, u r-rate limiting. ## Resilience — il-parti li l-juniors jaqbżu F'sistema distribwita kull network call *għad* tfalli xi darba. Uża Resilience4j biex twaqqaf servizz wieħed bil-mod milli jikkaskadja f'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)); } ``` Iċ-**circuit breaker** jinfetaħ wara fallimenti ripetuti, biex is-sejħiet jfallu malajr minflok ma jakkumulaw threads jistennew fuq dependency mejta. ## Għaliex huwa importanti L-intervisti senior jistħarrġu l-maturità fis-sistemi distribwiti. Li ssemmi discovery u config huwa l-minimu; id-differenza hija li titkellem dwar il-**fallimenti**: circuit breakers, timeouts, idempotency, u observability (distributed tracing b'Micrometer/Zipkin). Kandidati b'saħħithom ukoll jirreżistu — jinnutaw li l-microservices iżidu cost operazzjonali u monolith huwa spiss l-għażla t-tajba sakemm l-iskala titlob mod ieħor.

Il-partijiet li jiċċaqilqu

Resilience — il-parti li l-juniors jaqbżu

Għaliex huwa importanti

Mistoqsijiet relatati