Spring集成的可行性

发布于 2024-10-20 00:53:41 字数 247 浏览 2 评论 0原文

我是 Spring Integration 的新手。我有一些关于 Spring Integration 的问题,

  • 其中有哪些实时场景 哪个 Spring 集成可以 实施的 ?
  • 创建一个有什么好处 额外的弹簧集成层?
  • 如果没有邮件系统 spring 实现,可以 spring 积分仍可用于 一体化 ?

是不是像Spring Integration一样可以连接用两种不同语言开发的两个系统?

I am new to Spring Integration .There a few questions I have regarding spring integration

  • What are some real time scenarios in
    which spring integration can be
    implemented ?
  • What is the advantage of creating an
    extra spring integratio layer ?
  • If a mailing system is not
    implemented in spring , can spring
    integration still be used for
    integration ?

Is it something like spring integration can connect two systems developed in two different languages?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

奶气 2024-10-27 00:53:41

哪些实时场景可以实现spring集成?

我想说它最适合构建一个
使用管道的应用程序和
过滤器架构,主要用于
应用程序内架构和
设计。通过内部应用程序,我的意思是
“在应用程序内”。正适合
对于内部应用程序,因为
基于的轻质管道(通道)
util.concurrent 类。为了
例如 DirectChannel 是一个简单的
以及将两者分开的逻辑方法
处理工作流程中的节点,无需
队列的开销(不是 jms
队列)。

它确实支持之间的交互
通过网关的应用程序
适应各种消息机制
(如 Web 服务、JMS 等)。所以
应用程序不必转向
其他一些框架
应用程序间交互。

创建额外的 spring 集成层有什么好处?

如果您想要分离,它很有用
关注点、松散耦合和
灵活性

如果邮件系统不是用spring实现的,还可以使用spring集成进行集成吗?

我不明白这个问题,抱歉。

像Spring Integration这样的东西可以连接用两种不同语言开发的两个系统吗?

您的意思是,与基于非 Java 平台的另一个系统进行交互?这也可以实现,但主要不是因为 Spring Integration,而是通过将 Spring Integration 与现有的消息交换机制(如 WebServices、JMS 等)结合使用。如果需求只是 2 个应用程序之间的点对点消息传递,Spring集成不会有多大用处(除非在这样的对话中存在某种有趣的工作流程)。

What are some real time scenarios in which spring integration can be implemented ?

I would say its best for building an
application using the pipes and
filters architecture, primarily for
intra-application architecture and
design
. By intra-application, i mean
'within an application'. It is suited
for intra-application because of the
light-weight pipes(channels) based on
the util.concurrent classes. For
example the DirectChannel is a simple
and logical way to separate two
processing nodes in a workflow without
an overhead of a queue (not the jms
queue).

It does support interaction between
applications through gateways that
adapt to various messaging mechanisms
(like WebServices, JMS etc). So the
application doesn't have to turn to
some other framework for
inter-application interaction either.

What is the advantage of creating an extra spring integratio layer ?

Its useful if you want separation of
concerns, loose coupling and
flexibility
.

If a mailing system is not implemented in spring , can spring integration still be used for integration ?

I don't understand the question, sorry.

Is it something like spring integration can connect two systems developed in two different languages?

You mean, interact with another system that's based on a non-java platform? That can be achieved too, but not primarily because of Spring Integration but by using Spring Integration with existing mechanisms for exchanging messages like WebServices, JMS etc. If the requirement is just a point-to-point messaging between 2 applications, Spring Integration is not going to be of much use (unless there is an interesting workflow of sorts in such a dialogue).

离不开的别离 2024-10-27 00:53:41

而且,您还可以查看 https ://spring.io/blog/2011/02/24/green-beans-getting-started-with-spring-integration 介绍了 Spring Integration 以及基本范例。它会帮助您开始,然后您就可以开始理解示例等等。

And, also, you might check out https://spring.io/blog/2011/02/24/green-beans-getting-started-with-spring-integration which introduces Spring Integration as well as the basic paradigms. It'll get you started and then you can start to make sense of the samples and so on.

梦晓ヶ微光ヅ倾城 2024-10-27 00:53:41

真实的场景不胜枚举。 Spring Integration 是一个框架,允许您基于企业集成模式构建消息驱动系统。
请注意,当我说消息传递时,我并不是指 JMS 等远程消息传递或类似的东西。消息传递首先是一种架构范例(模式),它允许您构建松散耦合且可扩展的系统,例如此处描述的系统:http://blog.springsource.com/2010/03/18/eip-loan-broker-reference-implementation-part- 1/
Spring Integration 还提供远程适配器(TCP、HTTP、MAIL 等)来与远程系统集成。我们有许多示例,您可以查看以获取更多详细信息 http ://blog.springsource.com/2010/09/29/new-spring-integration-samples/

我想通过阅读这些文章你会明白“优势是什么”。我现在想说的是,在我看来,优势在于框架本身。通过使用它,您将无需编写集成代码。

“如果一个邮件系统不是用spring实现的,还可以用spring集成进行集成吗?” - 我不确定我是否理解这个问题。 Spring Integration 使用 JavaMail API 与电子邮件服务器进行通信(发送和接收)。您能详细说明一下吗?

The real scenarios are to many to mention. Spring Integration is a framework that allows you to architect message-driven systems based on Enterprise Integration Patterns.
Note, when I say Messaging I am not implying remote messaging such as JMS or anything like that. Messaging first and foremost is an is an architectural paradigm (pattern) which allows you to build loosely coupled and scalable systems such as the one described here: http://blog.springsource.com/2010/03/18/eip-loan-broker-reference-implementation-part-1/
Spring Integration also provides remote adapters (TCP, HTTP, MAIL etc.) to integrate with remote systems. We have many samples that you can go through to get more details http://blog.springsource.com/2010/09/29/new-spring-integration-samples/

I think by going through the articles you'll get the sense of "what is the advantage". ALl I want to state now is that IMO the advantage is the framework itself. By using it you'll spare yourself from writing integration code.

"If a mailing system is not implemented in spring , can spring integration still be used for integration ?" - I am not sure I understand the question. Spring Integration is using JavaMail API to communicate with emails servers (both send and receive). Could you please elaborate?

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文