blocks|key|879448|text|为什么不使用嵌入式数据库呢？选项包括：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|879449|879450|H2|unordered-list-item|offset|length|879451|HSQL|879452|Derby|879453|879454|只需将jar文件包含在webapps类目录中，并照常配置JDBC+URL即可。|879455|非常适合演示，当您想要切换到更大的数据库服务器时，可以很容易地进行替换|879456|entityMap|0|LINK|mutability|MUTABLE|url|http://www.h2database.com/html/main.html|1|http://hsqldb.org/|2|http://db.apache.org/derby/^0|0|0|0|2|0|0|0|4|1|0|0|5|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|14|8|@]|9|@$F|15|G|16|1|17]]|A|$]]|$1|H|3|I|5|E|7|18|8|@]|9|@$F|19|G|1A|1|1B]]|A|$]]|$1|J|3|K|5|E|7|1C|8|@]|9|@$F|1D|G|1E|1|1F]]|A|$]]|$1|L|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1H|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1I|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]|10|$5|T|U|V|A|$W|11]]]]

Why not use an embedded database? Options are:

<ul>
<li><a href="http://www.h2database.com/html/main.html" rel="nofollow">H2</a></li>
<li><a href="http://hsqldb.org/" rel="nofollow">HSQL</a></li>
<li><a href="http://db.apache.org/derby/" rel="nofollow">Derby</a></li>
</ul>

Just include the jar file in the webapps classdir and configure the JDBC URL as normal.

Perfect for demos and easy to substitute when you want to switch to a bigger database server

blocks|key|4546558|text|我会简单地将其存储在文件系统上的一个文件中。可以使用嵌入式数据库或类似的东西，但对于一条消息，一个文件就可以了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4546559|我建议您将文件存储在应用程序目录之外。它可能就在它旁边，但不要把它存储在你的"webapps/“目录中，或者类似的东西里。|4546560|您可能还需要管理并发性。全局(静态)读/写锁应该可以做得很好。|4546561|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|$]]

I would simple store that in a file on a filesystem. It's possible to use an embedded database, or something like that, but for 1 message, a file will be fine.

I'd recommend you store the file outside of the application directory.
It might be alongside (next to) it, but don't go storing it inside your "webapps/" directory, or anything like that.

You'll probably also need to manage concurrency. A global (static) read/write lock should do fine.

blocks|key|2947184|text|我会使用JNDI。为什么要过于复杂呢？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2947185|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would use JNDI. Why over-complicate?

blocks|key|1792486|text|多个选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1792487|向文件系统写入一些东西--非常适合持久化。有点慢。主要缺点是它可能必须是共享文件系统，因为任何类型的集群都不能很好地处理这一点。然后你就会遇到文件锁定问题。非常容易实现|1792488|嵌入式DB+-与仅写入文件系统类似的优点和缺点，但可能更好地处理锁定/事务问题。实现起来有点困难。|1792489|分布式缓存-类似Memcached+-比文件快一点，虽然不多。处理集群和锁定问题。然而，它不是持久的。对于短时间的webapp重启来说相当可靠，但绝对不是100%25。更难的实现，再加上你需要另一台服务器。|1792490|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Multiple options.

Write something to the file system - Great for persistence. A little slow. Primary drawback is that it would probably have to be a shared file system, as any type of clustering wouldn't deal well with this. Then you get into file locking issues. Very easy implementation

Embedded DB - Similar benefits and pitfalls as just writing to the file system, but probably deals better with locking/transactional issues. Somewhat more difficult implementation.

Distributed Cache - Like Memcached - A bit faster than file, though not much. Deals with the clustering and locking issues. However, it's not persistent. Fairly reliable for a short webapp restart, but definitely not 100%. More difficult implementation, plus you need another server.

We have a utility spring-mvc application that doesn't use a database, it is just a soap/rest wrapper. We would like to store an arbitrary message for display to users that persists between deployments. The application must be able to both read and write this data. Are there any best practices for this?

How do I save server state between webapp deployments not relying on a database?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我们有一个实用的spring-mvc应用程序，它不使用数据库，它只是一个soap/rest包装器。我们希望存储一条任意消息，以便在部署之间持续显示给用户。应用程序必须能够读取和写入此数据。这方面有什么最佳实践吗？

问如何在不依赖数据库的webapp部署之间保存服务器状态？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在不依赖数据库的webapp部署之间保存服务器状态？EN