我目前正在进行一个构建微服务的项目，并且正在尝试从更传统的spring boot转变 RestClient 使用netty和 WebClient 作为http客户端，以便连接到后端系统。
这对于带有restapi的后端来说是很好的，但是实现起来仍然有一些困难 WebClient 连接到soap后端和oracle数据库的服务，后者仍然使用传统的jdbc。
我设法在网上找到了一些关于jdbc调用的解决方法，这些方法使用并行调度程序来发布阻塞jdbc调用的结果：

//the method that is called by @Service
@Override
public Mono<TransactionManagerModel> checkTransaction(String transactionId, String channel, String msisdn) {
    return asyncCallable(() -> checkTransactionDB(transactionId, channel, msisdn))
            .onErrorResume(error -> Mono.error(error));
}

...

//the actual JDBC call
private TransactionManagerModel checkTransactionDB(String transactionId, String channel, String msisdn) {
...
    List<TransactionManagerModel> result = 
                    jdbcTemplate.query(CHECK_TRANSACTION, paramMap, new BeanPropertyRowMapper<>(TransactionManagerModel.class));
...
}

//Generic async callable
private <T> Mono<T> asyncCallable(Callable<T> callable) {
    return Mono.fromCallable(callable).subscribeOn(Schedulers.parallel()).publishOn(transactionManagerJdbcScheduler);
}

我觉得这很管用。
而对于soap调用，我所做的是将soap调用封装在 Mono 而soap调用本身正在使用 CloseableHttpClient 这显然是一个阻塞的http客户端。

//The method that is being 'reactive'
public Mono<OfferRs> addOffer(String transactionId, String channel, String serviceId, OfferRq request) {
...
    OfferRs result = adapter.addOffer(transactionId, channel, generateRequest(request));
...
}

//The SOAP adapter that uses blocking HTTP Client
public OfferRs addOffer(String transactionId, String channel, JAXBElement<OfferRq> request) {
...
    response = (OfferRs) getWebServiceTemplate().marshalSendAndReceive(url, request, webServiceMessage -> {
            try {
                SoapHeader soapHeader = ((SoapMessage) webServiceMessage).getSoapHeader();

                ObjectFactory headerFactory = new ObjectFactory();
                AuthenticationHeader authHeader = headerFactory.createAuthenticationHeader();
                authHeader.setUserName(username);
                authHeader.setPassWord(password);

                JAXBContext headerContext = JAXBContext.newInstance(AuthenticationHeader.class);
                Marshaller marshaller = headerContext.createMarshaller();
                marshaller.marshal(authHeader, soapHeader.getResult());
            } catch (Exception ex) {
                log.error("Failed to marshall SOAP Header!", ex);
            }
        });
        return response;
...
}

我的问题是：这个soap调用的实现是否足够“被动”，以至于我不必担心某些调用在微服务的某个部分被阻塞？我已经实现了React式堆栈调用 block() 显式将抛出异常，因为使用netty时不允许这样做。
或者我应该适应平行的用法 Schedulers 在soap调用中也是如此？