blocks|key|773707|text|那得看情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|773708|REST提供了两个服务之间更松散的耦合，通常是首选的方法。|773709|如果您有许多查询，并且调用REST的性能可能是一个问题，那么数据库视图将是有意义的。|773710|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

It depends. 

The REST API provides I looser coupling between the two services and is usually the preferred way.

The database view would make sense if you have many queries and the performance calling the REST API could be an issue.

blocks|key|1922407|text|我想说的是，从领域驱动的设计角度来看(微服务可以被视为域)，其他域不应该知道数据是如何存储/结构的(有界上下文)。因此，我将投票支持REST。另一个问题是，如果您的表/视图结构发生了更改，怎么办？这将导致其他微服务的急剧变化。使用REST，您可以更改路由的基本代码，而不会困扰您的用户。如果必须使用存储过程(或其他与数据库相关的性能调整)以获得更好的性能，则需要直接数据库查询。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1922408|entityMap^0|1U|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I would say that from a domain driven design perspective (and microservices could be considered as domains), other domains should not know anything about how your data is stored/structured (Bounded Context). Therefore I would vote for REST. Another point would be, what if your table/view structure changes? this would cause breaking changes in other microservices. With REST you can change the underlying code of your routes without bothering your consumer. Direct Database queries would be needed if you have to use stored procedures (or other database related performance tweaks) for better performance.

blocks|key|775917|text|为了在不同的微服务之间交换数据，我更喜欢REST，也许您可以在您的application.However中适应类似的东西--我用Java编写了这篇文章--您可以为您选择的任何语言编写代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|775918|希望这能有所帮助。|775919|public+final+class+MicroServiceDelegator+{

++++private+MicroServiceDelegator()+{
++++}

++++/**
+++++*+Calls+the+concerned+microservice+and+gets+the+response+JSON.
+++++*+
+++++*+@param+request+++++++the+request+object+containing+the+request+information
+++++*+@param+microserviceUri+++++++the+URI+to+make+a+request+to
+++++*+@param+requestMethod+specifies+either+GET+or+POST+request+method
+++++*+@return+JSON+string+response+from+the+micro+service
+++++*+@throws+Exception

+++++*/
++++public+static+final+String+callMicroService(final+HttpServletRequest+request,+final+String+microserviceUri,+final+RequestMethod+requestMethod)
++++++++++++throws+Exception+{

++++++String+responseBody;


++++//+Logic+to+identify+type+of+request+GET/POST
++++//+Build+any+HttpClient
++++//+Execute+the+Client

++++//+Build+responseBody+

++++//+Convert+response+to+JSON

++++++++return+responseBody;
++++}
++}|code-block|syntax|javascript|775920|例如，这可以用于任何微服务。|775921|@ResponseBody
++++@RequestMapping(method+=+RequestMethod.POST,+path+=+"/all",+produces+=+MediaType.APPLICATION_JSON_UTF8_VALUE)
++++public+String+getAllProducts(final+HttpServletRequest+request,+final+HttpServletResponse+response)+{

++++++++String+responseString+=+"";
++++++++try+{
++++++++++++responseString+=+MicroServiceDelegator.callMicroService(request,
++++++++++++++++"http://products-microservice"+%2B+"/all-products",
++++++++++++++++RequestMethod.POST);

++++++++}+catch+(Exception+e)+{
++++++++++++log.warn(e)
++++++++}
++++++++return+responseString;
++++}|775922|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I prefer REST in order to exchange data across different microservices, probably you can adapt something similar in your application.However I wrote this in Java you can write piece of code for any language of your choice.

Hope this helps.

<pre><code>public final class MicroServiceDelegator {

 private MicroServiceDelegator() {
 }

 /**
 * Calls the concerned microservice and gets the response JSON.
 * 
 * @param request the request object containing the request information
 * @param microserviceUri the URI to make a request to
 * @param requestMethod specifies either GET or POST request method
 * @return JSON string response from the micro service
 * @throws Exception

 */
 public static final String callMicroService(final HttpServletRequest request, final String microserviceUri, final RequestMethod requestMethod)
 throws Exception {

 String responseBody;


 // Logic to identify type of request GET/POST
 // Build any HttpClient
 // Execute the Client

 // Build responseBody 

 // Convert response to JSON

 return responseBody;
 }
 }
</code></pre>

This can be used in any microservice, for example

<pre><code>@ResponseBody
 @RequestMapping(method = RequestMethod.POST, path = "/all", produces = MediaType.APPLICATION_JSON_UTF8_VALUE)
 public String getAllProducts(final HttpServletRequest request, final HttpServletResponse response) {

 String responseString = "";
 try {
 responseString = MicroServiceDelegator.callMicroService(request,
 "http://products-microservice" + "/all-products",
 RequestMethod.POST);

 } catch (Exception e) {
 log.warn(e)
 }
 return responseString;
 }
</code></pre>

blocks|key|2765793|text|这个世界是不完美的，但是在一个完美的世界里，你的微型服务应该很少(如果有的话)直接彼此沟通。一种具有另一种知识的微服务将它们紧密地结合在一起，这比这种分布式体系结构更可取。这种耦合会影响CI/CD，降低容错能力，并在每个服务之外泄漏域信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2765794|在我们的系统中，唯一被(几乎)所有其他服务访问的微服务是授权服务，因此，如果需要，每个微服务都可以验证它接收到的凭据以执行特定的请求操作。服务之间的所有其他通信都是异步的，并通过集成总线(在本例中为RabbitMQ)传递。|2765795|在您提供的两个选项之间，REST可能更好，因为它至少在服务之间添加了一些抽象，但您可能会考虑仔细查看您的建模，看看是否可以减少服务之间的依赖，以消除需求。关于Auth0+这里关于依赖关系和这里的一篇像样的(虽然很老)的文章是一个很好的(很长的)讨论，它来自一个Spring项目负责人。|offset|length|2765796|entityMap|0|LINK|mutability|MUTABLE|url|https://auth0.com/blog/introduction-to-microservices-part-4-dependencies/|1|https://content.pivotal.io/springone-platform-2017/refactoring-to-a-system-of-systems-oliver-gierke^0|0|0|2D|2|0|2M|2|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]|$F|X|G|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

The world is imperfect, but in a perfect world your microservices should rarely (if ever) communicate directly with each other. One microservice having knowledge of another inherently couples them more tightly than is preferable for this distributed architecture. This coupling affects CI/CD, reduces fault tolerance and leaks domain information outside each service.

In our system, the only microservice accessed by (nearly) all others is the Authorization service so that if required, each microservice can validate the credentials it receives for a specific requested action. All other communication that occurs between services is asynchronous and passed along over our Integration Bus (RabbitMQ in our case).

Between the two options you presented, REST is probably better because it adds at least some abstraction between the services, but you might consider taking a hard look at your modeling to see if you can reduce dependencies between services to eliminate the need. Decent (though old) article on Auth0 <a href="https://auth0.com/blog/introduction-to-microservices-part-4-dependencies/" rel="nofollow noreferrer">here</a> about dependencies and <a href="https://content.pivotal.io/springone-platform-2017/refactoring-to-a-system-of-systems-oliver-gierke" rel="nofollow noreferrer">here</a> is a good (long) talk about this issue from a Spring Data project lead.

which is the best way between these two approches that allow two microservices to exchange data

1- Via Rest call.

2- Each microsevice expose its related data as a database's view ,so that it can be reached by other microservices using Spring JDBC template or JPA.

Notice that each microservice has its own (private) tables in the same database schema.

Thanks,

Microservices communication JDBC SQL VS REST

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在这两种方法之间，允许两个微服务交换数据的最佳方法是哪种方式？通过Rest呼叫。2-每个微服务将其相关数据公开为数据库视图，以便其他微服务可以使用Spring模板或JPA访问它。注意，每个微服务在同一个数据库模式中都有自己的(私有)表。谢谢,

问微服务通信JDBC与REST
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问微服务通信JDBC与RESTEN