Databases
StackOverflow2013
Postsdbo
POKeeping data in memory, Design approach
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POKeeping data in memory, Design approach
    primarykey
    data
    text
    <p>I have a problem where in I need to process some files with size in the range of few kbs up to 1 GB max. The use case is such that the input is in some flat file format where the data is stored in a single line, say some payment instructions. Application has to go through each payment instruction and form groups based on some grouping logic. At the end the groups has to be converted to another format(ISO 20022 xml) using which payment processing will be happening.</p> <p>The current design is such that, we have two tables where grouping criteria data is stored in one table and individual payment instruction is stored in another table (One to Many relationship from group Table to Payment Instruction Table). And in Step 1 : as and when we go through the flat file we identify the group it belongs to, and write to the database(bulk commit btw). </p> <p>In step 2: of batch processing the groups are read one by one and form the output xml and send to the destination.</p> <p>The issue I'm facing now is that writing to two tables and fetching from that is an overkill, if the entire thing can be done in memory.</p> <p>I'm thinking of an approach where in I can keep a HashTable(google guava (<a href="http://code.google.com/p/guava-libraries/" rel="nofollow">MapMaker</a>)) kind of caching, and the size of which I can specify, and once the cache reaches the upper limit I can write them into database tables (weave an aspect on the put to cache).</p> <p>In the same way while retrieving the entries I can first check in the cache for the key and if it not there, query the database.</p> <p>What is your opinion on this design approach(Is it another blunder or something which I can make practical and at the same time stable, and can scale).</p> <p>Why I thought of this is, we don't have big files coming in always, and we require these temperory tables only if we cannot process the entire file in memory and may lead to OutOfMemory problems.</p> <p>Could you please give some suggestions ?</p> <p>Thanks</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USnobody
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POKeeping data in memory, Design approach
      1. This table or related slice is empty.
      1. VTUpMod
    1. COFor the cost of developing a custom aspect oriented solution I bet you could buy several servers with enough RAM to handle the 1GB file in memory :) Sounds like a fund idea though!
      singulars
      1. POKeeping data in memory, Design approach
      1. USAffe
    2. COWriting an aspect is not that complicated, but in this case it's probably overkill, can't you simply wrap the hashmap in a class of your own that flushes to the db after a certain number of "add" and searches on the DB if the "get" does not result and already cached result? As any cache does more or less :D
      singulars
      1. POKeeping data in memory, Design approach
      1. USSimone Gianni
    3. CO@SimoneGianni see the problem is that I haven't seen a design like this anywhere else. So if I propose something like this will the BIG guys directly reject this for any other reason I don't forsee now, or do you think its a good approach to the problem in hand ?
      singulars
      1. POKeeping data in memory, Design approach
      1. USnobody
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload