Please enable JavaScript.

Coggle requires JavaScript to display documents.

Microservices - Coggle Diagram

- - - - Reduces the complexity in the microservice code by abstracting the common infrastructure related functionalities to a different layer.
      - Reduces code duplication in a Microservice architecture since you do not need to write configuration code inside each microservice.
      - Provide loose coupling between application code and the underlying platform.
- - - - Last n requests to consider for the decision.
      - How many of those should fail?
      - Timeout duration.
    - - Fallback.
        
        E.g. throw an error,
        
        Return fallback default response, some hard-coded value
        
        Cache
    - - Failing fast
        
        If you know that some endpoint will fail, don't wait for its failure, stop it right away
      - Fallback functionality
      - Automatic recovery
- - - - Exception-based Conditional Retry
        
        RetryConfig config = RetryConfig.custom() .maxAttempts(3) .waitDuration(Duration.of(3, SECONDS)) .retryExceptions(FlightServiceBaseException.class) .ignoreExceptions(SeatsUnavailableException.class) .build();
      - Predicate-based Conditional Retry
        
        RetryConfig config = RetryConfig.<SearchResponse>custom() .maxAttempts(3) .waitDuration(Duration.of(3, SECONDS)) .retryOnResult(searchResponse -> searchResponse .getErrorCode() .equals("FS-167")) .build();
    - - CheckedFunction0<List<Flight>> retryingFlightSearch = Retry.decorateCheckedSupplier(retry, () -> service.searchFlightsThrowingException(request)); try { System.out.println(retryingFlightSearch.apply()); } catch (...) { // handle exception that can occur after retries are exhausted }
    - - Exponential Interval
        
        RetryConfig config = RetryConfig.custom() .maxAttempts(6) .intervalFunction(IntervalFunction.ofExponentialBackoff(1000, 2)) .build();
      - Randomized Interval
        
        RetryConfig config = RetryConfig.custom() .maxAttempts(4) .intervalFunction(IntervalFunction.ofRandomized(2000)) .build();
    - - ScheduledExecutorService scheduler = Executors.newSingleThreadScheduledExecutor(); Supplier<CompletionStage<List<Flight>>> completionStageSupplier = () -> CompletableFuture.supplyAsync(() -> service.searchFlights(request)); retry.executeCompletionStage(scheduler, completionStageSupplier) .thenAccept(System.out::println);
    - - Retry.EventPublisher publisher = retry.getEventPublisher(); publisher.onRetry(event -> System.out.println(event.toString())); publisher.onSuccess(event -> System.out.println(event.toString()));
      - Similarly, RetryRegistry also has an EventPublisher which publishes events when Retry objects are added or removed from the registry.
    - - First, we create RetryConfig and RetryRegistry and Retry as usual. Then, we create a MeterRegistry and bind the RetryRegistry to it:
        
        MeterRegistry meterRegistry = new SimpleMeterRegistry(); TaggedRetryMetrics.ofRetryRegistry(retryRegistry).bindTo(meterRegistry);