Only the beginning of a drawn map, and so have the time may complement description.
1. Core issues: data will increase with the end of time and the amount of a single two variables and growth.
Figure 2. The different programs at all stages of primitive way is to add a total of five, sixth final plan was not drawn. A concession to the last two total binding. So I have time to write a detailed. The first three apply only to the business of exploration programs between formative years starting from the point of view of reducing the amount of data, the latter two is underway for high availability with multiple data sources and unlimited expansion angle. It is growing to maturity stage. Applicable to the different stages of the program does not make sense, cost is always a need to make the corresponding income return.
Scheme One: 02-1 FIG third
Option II: IV of FIG. 02-1
Program III: 02-1 V in FIG.
Final data flow diagram:
Remove the default cache service is not free to expand the other can be unlimited expansion, in fact, can continue to optimize the default cache is unlimited expansion.
PS
In short, you will find that special feel like in a database table-level sub-library sub-sub-sub-library and abstract a table on a program service. This is so because the resources allocated to DB is limited. In the case of DB convenient investment uneconomical. If your DB server performance is quite high. Reduction in the amount of data that can solve the problem, do not need to follow the procedure of abstraction.
Secondly, you will not wonder how smart ah? Automatic data-aware of how hot do? The need to support big data technology to collect various performance indicators and data services index calculated in real time. Then triggered by certain loading conditions. After the return to their roots still needs to be given the conditions to be loaded into the cache area, only one is active trigger another notification class is calculated after the passive trigger. I felt a sense of a no. In the absence of thought conditions magnify the problem is not a principle. Priority to meet "current business" scene needs is the most correct.