英文:
What is the best way to benchmark Hazelcast's speed to data retrieval, comparing with direct DB calls / RESTful service calls?
问题
背景： 我的团队在过去的十多年中一直在维护一系列经典的ASP/ASP.NET应用程序。最近，我的公司进行了一次重新组织，团队和经理要么被裁员，要么被调换了位置。我的新经理正在推动在未来一两年内重构我们整个应用程序组合，将其迁移到Java/Spring Boot，以符合公司的基础架构标准。我们今天的大多数应用程序通过MSSQL或Oracle SQL数据库执行ETL任务的存储过程，还有一些分别通过SOAP和REST连接到API。
目标： 作为重写的一部分，我被要求帮助决定如何处理我们应用程序的数据检索，并确定是否存在任何改进的机会。我想尝试使用Hazelcast（服务器），并“证明”它在性能上优于直接DB / REST调用等传统数据检索方法。
问题： 实现我的目标（对Hazelcast进行基准测试）的最佳方法是什么？我最初的想法是使用Java和Spring创建一个概念验证，以测试a.) 直接DB调用的平均速度，b.) RESTful API调用的平均速度，以及c.) 从Hazelcast检索的平均速度。我会确保所有三个测试中的记录集是一致的。这种方法正确吗，还是我在过度复杂化或过于简化？是否已经有类似的东西可以用来演示相同的内容？
（请注意，我理解Hazelcast并不意味着取代原始的记录源，而是提供数据缓存，以便更快地检索后续的调用。我希望证明从缓存中检索的确实比仅执行另一个DB / API调用要快。）
英文:
Background: My team has been maintaining a mix of classic ASP/ASP.NET apps for over a decade. My company recently had a re-org in which teams and managers were either laid off or swapped around. My new manager is pushing for a refactoring of our entire app portfolio over the coming year or two to Java/Spring-boot to meet company infrastructural standards. Most of our apps today perform ETL tasks via sprocs from MSSQL or Oracle SQL databases, with a few connecting to APIs via SOAP and REST respectively.
Goal: As part of this rewrite, I've been asked to help make a decision about how we handle data retrieval for our apps and to determine if there are any opportunities for improvement. I want to try out Hazelcast (server) and "prove" it out-performs traditional data-retrieval methods like direct DB / REST calls.
Question: What would be the best approach for achieving my goal (benchmarking Hazelcast)? My initial idea is creating a proof of concept with Java & Spring to test a.) the average speed of a direct DB call, b.) the average speed of a RESTful API call, and c.) the average speed of retrieval from Hazelcast. I would make sure the record set is consistent across all three tests. Is this the right approach, or am I over/under complicating it? Is there already something built out I can use to demonstrate the same?
(Note, I understand Hazelcast is not meant to replace the original source of record, but provide data caching for quicker retrieval of subsequent calls. I want proof that it is indeed quicker to retrieve from the cache rather than just doing another DB/API call).
答案1
得分: 1
这也在Google Group上同一个问题的讨论中有所涵盖 - https://groups.google.com/g/hazelcast/c/Q6LpR8o6qII
英文:
This is also covered on the same question on Google Group - https://groups.google.com/g/hazelcast/c/Q6LpR8o6qII
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论