Java开发网 - 请教一个基于J2EE的系统设计

Topic: 请教一个基于J2EE的系统设计

1.请教一个基于J2EE的系统设计

Posted by: wsfx
Posted on: 2004-09-18 15:47

由于小弟没有设计过大系统，想请教以下大家。
现在有一个系统，特点如下：
1.数据量大，记录都是百万级的，有个别表是千万级的；
2.事务长，操作复杂，通常完成一个事务要几分钟，而且好像不便拆分；
3.并发性很强，在线用户通常在300多。
基于性能的考虑，现在的疑惑是：
1.由于考虑到性能关系，现在的初步想法是不敢用CMP，BMP，Hibernate等持久化技术，直接SessionBean+JDBC是否可行？
2.因为有些事务很复杂，在短时间内读写数据库非常频繁，如果将这些逻辑放在EJB里完成，势必造成性能影响；但如果将业务逻辑封装在数据库的存储过程中，那我们用J2EE Application Server干嘛？
3.有些事务执行时间要几分钟，用户多时，这对数据库连接的并发性也是个挑战，有更好的设计方案？
大家有没有别的更好的方案，保证系统的性能？
望不吝赐教，谢谢！

2.Re:请教一个基于J2EE的系统设计 [Re: wsfx]

Copy to clipboard

Posted by: didongusa
Posted on: 2004-09-19 09:36

I suggest you choose a reliable framework.

SOL1. The EJB is still reliable. No BMP, No Hibernate, No JDBC. Use Session facase and CMP to persiste. Using struts to filter readers. If over 300 users make transactions at the same time, use cluster application server and DB to balance. 300 is not big. Some Server provide CMP catch to fast the transaction, you can make a try.

SOL2. Use PSP as front and cluster database to handle every business. The only trouble is the database IO. Maybe you don't like this because no where to show off your top java skills.

SOL3. Struts + SQLJ, in this situation, the DB is a direct model. Whether user access db or not depends on how did you organize, you control everything such as who has priority to get transact, or even catch the data for fast access. Because a lot of coding to be done, this solution is buggy and slow. The only bottle neck is the DB access.

SOL4. Using an object mapping frame work to build a deployable model and deploy to the clusterable application server which also provide catch and message utility. The struts play the front. No EJB, you can't put them together to complex the situation. The plain javabean is a good solution for this kind of frame work.

SOL5. Struts + EJB + Hibernate. This is bitter for me, but who knows, you can make a try, if it works that's good.

Just stay on your track.