Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

请教性能 #40

Open
jishuxx opened this issue Mar 6, 2023 · 2 comments
Open

请教性能 #40

jishuxx opened this issue Mar 6, 2023 · 2 comments

Comments

@jishuxx
Copy link

jishuxx commented Mar 6, 2023

我看整体架构依赖数据库,有点担心性能是否能应对高并发?我理解应该设计为分层架构,分不同模块,按需引入。底层的执行引擎不依赖数据库,上层的应用层按需引入状态模块。

@lthaoshao
Copy link
Collaborator

1、引入数据库主要是为了保证流程的存储和流程执行过程的记录,以及保证在中断后能够继续执行;可参考activiti。
2、在性能上,主要看并发量以及数据库层面的压力;
3、会考虑引入缓存,减少数据库交互;

@jishuxx
Copy link
Author

jishuxx commented Mar 6, 2023

1、引入数据库主要是为了保证流程的存储和流程执行过程的记录,以及保证在中断后能够继续执行;可参考activiti。 2、在性能上,主要看并发量以及数据库层面的压力; 3、会考虑引入缓存,减少数据库交互;

理解,to B场景我感觉是可以的。如果支持toC场景,不清楚TPS大概都能到多少,to C场景我理解可能要用内存工作流(无状态),类似compileflow这样的,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants