Architecture for Dashboard in Web Application (Java based)

Question

I have the requirement for building an Activity Dashboard for users when they log into the web application. The Dashboard will show various “portlets” of business transactions which have taken place since they last logged in, etc.

I was wondering what the ideal architecture for such a system should be? If the dashboard is to have 7-10 different portlets of data, should each portlet do a DB call on the specific individual table to get the latest transactions? Or should there be a common activity table where when a business transaction executes it dumps data (who, what, where) into this common table (synchronous or via a messaging queue) and then this is the only table which is then queried by the dashboard?

Which solution would be better for high performance and scalability?

Thanks in advance for your input.

SP

Answer 1

答案取决于应用程序生成的事件等的数量。但是我会针对不同的Portlet使用不同的活动表，并具有适当的索引。