• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Optimal Data Structure for Concurrent Reads and Writes

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello All,
Which is the most optimal, performance efficient data structure available in java for concurrent read and writes with and without hashing, such that concurrent reads always return concurrent writes?
 
Sheriff
Posts: 3063
12
Mac IntelliJ IDE Python VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, and welcome to Java Ranch!

The problem with this question is that it sounds very much like a homework assignment, and we're very sensitive about being asked to do other people's homework for them. Maybe you could discuss some of the possible architectures you have in mind, and which one you think would be best.
 
Bartender
Posts: 10780
71
Hibernate Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Tanujasri Bhatkal wrote:Which is the most optimal, performance efficient data structure available in java for concurrent read and writes with and without hashing, such that concurrent reads always return concurrent writes?


Welcome Tanujasri.

I'm afraid your question doesn't have any meaning without some context. The fact is that concurrent reads can't always return concurrent writes because they're concurrent (unless you have some sort of queuing system that prioritises writes over reads, which seems a bizarre thing to do). The best you can hope for is some guarantee of consistency; and that, again, will depend very much on context.

As Greg says, some idea of what you've researched would be helpful.

Winston
 
reply
    Bookmark Topic Watch Topic
  • New Topic