DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Delegated Transport, Forked Authorization: Where Chat and AI-Agent Integrations Actually Break
  • A Non-Expiring AKS Deployment Token Could Read Secrets Across Three Namespaces
  • The Permission Was Valid. The Action Was Not Authorized.
  • Why AI Agents Need a Shared Enterprise Ontology

Trending

  • Moving 900+ GB of Prometheus Without a Cutover Weekend
  • To Switch, or Not to Switch the AI Model
  • PWA on iOS, Part 2: HTTPS, Manifest and Service Worker
  • How You Clear Your HTML5 Canvas Matters

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Data Engineering
  3. Databases
  4. Asynchronous API Calls: Spring Boot, Feign, and Spring @Async

Asynchronous API Calls: Spring Boot, Feign, and Spring @Async

Learn how to make asynchronous API calls from Spring Boot using Spring Cloud OpenFeign and Spring @Async to reduce the response time to that of a one-page call.

By 
Mukut Bhattacharjee
·
Updated Sep. 28, 22 · Code Snippet
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
33.3K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

The requirement was to hit an eternal web endpoint and fetch some data and apply some logic to it, but the external API was super slow and the response time grew linearly with the number of records fetched. This called for the need to parallelize the entire API call in chunks/pages and aggregate the data.

Our synchronous FeignClient:

Java
 
@FeignClient(url = "${external.resource.base}", name = "external")
public interface ExternalFeignClient {

    @GetMapping(value = "${external.resource.records}", produces = "application/json")
    ResponseWrapper<Record> getRecords(@RequestHeader Map<String, String> header,
                                            @RequestParam Map<String, String> queryMap,
                                            @RequestParam("limit") Integer limit,
                                            @RequestParam("offset") Integer offset);


}


Let's prepare the configuration for the async framework:

Java
 
@EnableAsync
@Configuration
public class AsyncConfig {
 
	@Bean
	public Executor taskExecutor() {
		ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
		executor.setCorePoolSize(5); // set the core pool size
		executor.setMaxPoolSize(10); // max pool size
		executor.setThreadNamePrefix("ext-async-"); // give an optional name to your threads
		executor.initialize();
		return executor;
	}
  
}  


Now to make the feign clients work in asynchronous mode, we need to wrap them with an async wrapper returning a CompletableFuture.

Java
 
@Service
public class ExternalFeignClientAsync {
  
	@Awtowired
	private ExternalFeignClient externalFeignClient;

	@Async
	CompletableFuture<ResponseWrapper<Record>> getRecordsAsync(Map<String, String> header,
                                            Map<String, String> header,
                                            Integer limit,
                                            Integer offset){
		CompletableFuture.completedFuture(externalFeignClient.getRecords(header,header,limit,offset));
	}

}


Now our async feign client is ready with a paginating option using the limit and offset. Let's suppose we know or we figure out by some means (out of scope for this article), the total number of records available. We can then consider a page size for each call and figure out how many API calls we need to make and fire them in parallel.

Java
 
@Service
public class ExternalService {
  
  @Autowired
  private ExternalFeignClientAsync externalFeignClientAsync;
  
  List<Record> getAllRecords(){
    
    final AtomicInteger offset = new AtomicInteger();
    int pageSize = properties.getPageSize(); // set this as you wish
    int batches = (totalCount / pageSize) + (totalCount % pageSize > 0 ? 1 : 0);
    return IntStream.range(0, batches)
                    .parallel()
                    .mapToObj(i -> {
                        final int os = offset.getAndAdd(pageSize);
                        return externalFeignClientAsync.getRecordsAsync(requestHeader, queryMap, fetchSize, os);
                    })
                    .map(CompletableFuture::join)
                    .map(ResponseWrapper::getItems)
                    .flatMap(List::stream)
                    .toList();
  }
}
  


And voila!

The entire API call is now broken down into pages and fired asynchronously, with the overall response time reduced to the time taken by a one-page call.

API

Opinions expressed by DZone contributors are their own.

Related

  • Delegated Transport, Forked Authorization: Where Chat and AI-Agent Integrations Actually Break
  • A Non-Expiring AKS Deployment Token Could Read Secrets Across Three Namespaces
  • The Permission Was Valid. The Action Was Not Authorized.
  • Why AI Agents Need a Shared Enterprise Ontology

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook