是否需要一个不基于 Spring/Tomcat 的 Java 7 云服务器框架?

发布于 2024-08-17 14:23:30 字数 355 浏览 10 评论 0原文

是否存在对小型、轻量级、基于 Java 7 的开源项目的需求,旨在使云服务更加优雅?我一生中编写过多个服务器,并且很好奇是否有必要这样做。

我的想法是保持简单、轻量级,并使用 Java 7 NIO 2 功能进行网络通信。我还考虑使用广播地址在机架解决方案 (MBONE) 中的服务器之间进行基于本地云的通信,或者使用基于序列化的通信协议。

我不想使用 Spring 或 Tomcat,因为它们太重了,而且它们是用较旧的 Java 技术编写的。此外,我不想使用另一个 Apache 项目,因为它过于依赖 Apache 技术。这里的关键词是“小型”、“轻量”、“便携”和“高效”。

也许这甚至有可能作为后台服务器,甚至移动云网络安装和使用在移动设备中。

Is there a demand out there for a small, lightweight, Java 7 based open source project that is geared toward making Cloud services more elegant? I have written several servers in my lifetime, and was curious if there was a need for this.

My thoughts were to keep it simple, lightweight, and use the Java 7 NIO 2 functionality for network communications. I was also thinking of using either a broadcast address for local cloud based communications between servers in a rack solution (MBONE) or a serialization-based communications protocol.

I don't want to use Spring or Tomcat, as they are overweight, and they are written on older Java technology. Furthermore, I don't want to use another Apache project because it's too dependent on Apache technologies. Keywords here are "small", "lightweight", "portable", and "efficient".

Maybe this will even have the potential of being installed and used in mobile devices as background servers, or even mobile cloud networks.

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

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

发布评论

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

评论(1

身边 2024-08-24 14:23:30

从我自己的角度来看,没有。

  • 如果我想要一个轻量级的 servlet 服务器,我会使用 Jetty。
  • 如果我想要一个更强大、更通用的 Web 应用服务器,我会使用 Tomcat。
  • 如果我想要一个完整的 J2EE 服务器,我会使用 Glassfish。

所有这些当然都是经过充分验证的。如今内存足够便宜,我不太担心有点膨胀。这是 Java 应用程序的标准配置 :)

另外,我认为在移动设备上部署服务器技术是疯狂的。也许其他人有聪明的新想法,我认为移动设备应该与中央服务器通信。

我可能不想使用基于 J2EE 的 Java 7 服务器,至少是 servlet 部分,除非有人提出一个真正令人信服的替代方案。另一方面,我想知道您可以制作多小的兼容服务器。

最后,据我所知,Tomcat 已经(可选)支持 nio: http: //tomcat.apache.org/tomcat-6.0-doc/aio.html

纯属老顽固的个人观点。

From my own point of view, no.

  • If I want a lightweight servlet server, I use Jetty.
  • If I want a more powerful, versatile Web app server, I use Tomcat.
  • If I want a full J2EE server, I use Glassfish.

All of these are of course highly proven. Memory is cheap enough these days that I'm not very worried about a little bloat. That comes standard with Java apps :)

Also, I'd consider it crazy to deploy server technology on mobile devices. Maybe other people have bright new ideas, I think mobile devices should communicate with central servers.

I would probably not want to use a Java 7 server not based on J2EE, at least the servlet part, unless someone comes up with a really compelling alternative. On the other hand, I wonder how small you could make a compliant server.

Finally, as far as I know, Tomcat already (optionally) supports nio: http://tomcat.apache.org/tomcat-6.0-doc/aio.html .

Strictly a personal opinion from an old curmudgeon.

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