从 JBoss 4.2.x 迁移到 ....？
我工作的公司的主要应用程序在 JBoss 4.2.3（ejb2.1 规范）中部署和运行。它还广泛使用 JBPM 3.x。每个客户都有自己的服务器，通过HTTP（Struts2中的前端）访问应用程序。
我的任务是研究我们可以做些什么来踏入 2020 年……
乍一看，从 4.2.x 迁移到 JBoss EAP7 似乎需要大量工作（以及我所经历的反复试验）收集...）。我确实没有看到明确的迁移路径，除了一些帖子提到从 JBoss 4.x 迁移到 5，然后从那里迁移到 7.x 可能更容易。
即便如此，我也不是 100% 认为我们会从留在这个生态系统中受益匪浅（我们的大部分知识都将过时，因为配置、文件夹结构、注释等很可能从那时起已经发生了很大变化），而且我是担心我们最终可能会浪费大量时间试图使其发挥作用，并最终重写我们拥有的大部分内容。我想知道 2022 年您将如何解决这个问题？
您建议留在 JBoss 吗？转向另一种（更好？）服务器技术（也可以部署 JBPM）？利用这个机会彻底重新思考架构（例如：从单一应用程序转变为更分散的微服务等）？
注意：我们还需要继续支持当前现有的数据（客户的JBPM流程将逐步推出到最新版本）。为此，我想我们可以向 4.x 服务器添加一个 REST 层，新服务器将在适当的时候使用它。我想，随着我们逐渐将它们集成/添加到新技术中，我们也可能对大多数操作（不仅仅是 JBPM 相关）做类似的事情。这有意义吗？
我知道在不了解所有细节的情况下很难给出完整的答案，但无论如何我都想了解一下，或者让人们分享他们的经历，如果他们必须经历类似的事情。到目前为止，一切都是开放的。我们正在尝试了解我们有哪些选择以及每种选择需要多少投资。
The company where I work has its main application deployed and running in JBoss 4.2.3 (ejb2.1 spec). It also uses JBPM 3.x extensively. Each customer has its own server, and the application is accessed through HTTP (front end in Struts2).
I was tasked to look at what we could do to set foot in the 2020 decade...
At first glance, the migration from 4.2.x to JBoss EAP7 seems like it would involve a lot of work (and trial and error from what I gather...). I don't really see a clear path for the migration, except a few posts mentioning that it may be easier to move from JBoss 4.x to 5, and then move to 7.x from there.
Even so, I am not 100% we would benefit that much from staying in that ecosystem (most of our knowledge will be obsolete, since configurations, folder structure, annotations, etc. most probably have changed a lot since then), and I am afraid that we may end up wasting a lot of time trying to make it work and end up rewriting most of what we have. I was wondering how you would tackle this in 2022?
Would you suggest staying with JBoss? Move to another (better?) server technology (where JBPM could also be deployed)? Use this opportunity to rethink the architecture completely (ex.: go from a monolithic app to something a bit more fractured into micro-services, etc.)?
Note: We will also need to continue supporting currently existing data (customers' JBPM processes will be rolled out to the latest version gradually). For this, I was thinking we could add a REST layer to the 4.x server, that would be used by the new server when appropriate. We could also probably do something like this for most operations (not just JBPM related) I guess, as we gradually integrate/add them to the new tech.? Would that make sense?
I know it's hard to give a complete answer without knowing all the details, but I am asking anyway to get a pulse or to have people share their experiences if they had to go through a similar thing. As of now, anything is open. We are trying to see what kind of options we have and how much investment each would require.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论