Microservices架构模式是否类似于EJB 1.0？ [英] Is the Microservices architectural Pattern similar to EJB 1.0?

问题描述

我们使用微服务看到的是一个孤立的组件，通过线上协议将该组件通信到该组件的父消费者。

我们看到与EJB 1.0非常相似的模式。

我的问题是： Microservices架构模式是否类似于EJB 1.0？

解决方案

我从来没有直接使用过EJB，但是我已经与EJB团队合作，主要是创建与EJB服务进行交互（与服务器和客户端）交互的微服务器。

IMHO与EJB的最大区别在于它被创建来处理较大的应用程序。 EJB有许多方面和技术。当考虑到一个小的微服务器时，其中有些似乎过度杀伤。当项目规模较大时，这些技术的实施费用回报较高。再次，这是一个主观意见。在创建小型微服务器时，您会意识到架构的简单性，所使用的技术可以保持在最低限度。

根据所有内容，我认为可以有效地使用EJB在微服务环境中。关键是保持应用程序容器小巧灵活，能够轻松地通过HTTP与其他服务协同工作。

What we see with microservices is an isolated component, communicating over a protocol over the wire to a parent consumer of that component.

We see a very similar pattern with EJB 1.0.

My question is: Is the Microservices architectural Pattern similar to EJB 1.0?

解决方案

I have never worked with EJB directly but I have worked with EJB teams, mainly creating microservices that interacted (both as server and client) with the EJB services.

IMHO, the big difference with EJB is that it is created to handle larger applications. There are a many aspects and technologies that make up EJB. Some of them seem overkill when considering a small microservice. Those technologies have a higher return on the cost spent on implementing them when the project is bigger. Again, this is a subjective opinion. When creating small microservices you realize how simple the architecture is and that the technologies used can be kept to a minimum.

With all that said, I think EJB can be used effectively in a microservices environment. The key will be to keep the application containers small and nimble and able to easily work with other services over HTTP.

这篇关于Microservices架构模式是否类似于EJB 1.0？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！