This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of The Little Book of Impediments (e-book only) and have Tom Perry on-line!
See this thread for details.
Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Caching Design & Survey

 
Don Burke
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I've implemented caching in my data class. IMO it works great. There has been debate about its neccessity however..so i'd like to know who else has choosen to add caching and better yet, if anyone has passed the assignment with a caching implementation.

It would be really interesting to see what sun thinks about this.

The design i took was to store each record in an object and to have each object handle its own locking. Thus giving me record level locking as opposed to map / data class locking.

The data class has shared read, exclusive update/delete/create. When a record is modified the cache is first updated and then the cache is written to disk. I have heard of corruption issues..but is that really relevant? (atm i'm ironing out a deadlock in my create method...)

It would be great to have your thoughts on this design and to know who has passed the assignment using caching.

cheers

Don
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 12014
220
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Don,

I know that there have been members here who have passed using cacheing, the trouble is that having passed, most of them move on to other forums, so it is hard to get a response to a question like yours .

I like the idea of record level locking - it is rarely mentioned here though.

Are you writing the entire cache out on an update, or just the changed / added record?

Regards, Andrew
 
Anthony James
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi
I have written most of my B&S assignment and have now found this forum which is really helpful.
My design used caching as Don has mentioned and I have used a row-level locking too.
I also have implemented a 2 tier design although after reading the assignment and discussions here I would be tempted, if I had the time, to rewrite for a 3 tier.
I also included too much functionality and in particular had a difficulty trying to decide whether a CSR should be able to book a number of contractors rather than the whole record. This caused me much difficulty in a number of areas and couldn't decide whether this was actually something Sun would require. Fortunately I found a post of Andrews where he gave his opinion that this was outside the scope.

I am interested if Don is still around how he got on, and also, how did the deadlock manifest itself in the create?

Thanks a lot
Tony
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic