I don't have much background on AOP and have never used the same in any of my projects. But I do have the basic understanding of the cross-cutting concerns and the power and applicability of AOP.
Having set the context of my exposure to AOP, I was wondering about not so strange requirement of compressing the data in memory and modelling it as an Aspect of the system.
One of my applications queries out thousands of record from the database and keeps it in memory, since a lot of viewing and summary generation takes place. To optimize the memory requirement of this application, various options were discussed and one of those was to keep the data compressed.
Now how much part of this data can be compressed so that performance is not severely hit by it are some questions which needs to be worked out. But generally thinking from a design view-point I thought of modeling it as an Aspect, so that it can be configured and applied at API level without doing much code changes and making the whole deal seamless.
So just wondering, how apt would it be from the AOP perspective and whether any such framework already exists which support InMemory DataCompression in applications ?
Subscribe to:
Post Comments (Atom)
3 comments:
At the outset, i must profess my novice status in this field.
This is indeed a good idea. However, isn't it possible that DB vendors may themselves start coming out with techniques that present data to the client in a standard compressed format? Is there already such a facility provided by any of the vendors? In any case, for J2EE users, the JDBC APIs would need to incorporate the vendor provided facility. Perhaps having the vendors do it would be a faster solution.
-..
p.s. How much did the sandwiches cost?
Looks good! Well done. All the best!
- nikhildx-blog.blogspot.com u
spaghetti alla carbonara
Nice post and this fill someone in on helped me alot in my college assignement. Thank you on your information.
Post a Comment