History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: COR-748
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Carl Rosenberger
Reporter: Anat Gafni
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
db4o Core

Evaluate and estimate multi-transactional support for clustered ObjectContainers

Created: 02/Aug/07 09:44 PM   Updated: 08/Aug/07 05:14 PM  Due: 08/Aug/07
Component/s: Client/Server
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Original Estimate: Not Specified
Remaining Estimate: 0h
Time Spent - 4h
Time Spent: 4h
Time Spent - 4h

Environment: .NET

Peers: Andrew Zhang
Order: 2
Iteration: 3
Original IDS Estimate: 1
Resolution Date: 08/Aug/07 05:14 PM
Labels:
Participants: Anat Gafni and Carl Rosenberger
Number of Attachments: 0
Number of Comments: 0


 Description  « Hide
Cluster of ObjectContainers / Federation:
(Maik can provide more details)

Customer needs to rollover their database containers at regular intervals determined by user needs (file size or time based) and to split meta-data from mass-data in different containers. So db4o needs to provide some kind of transactional clustering with N-phase-commits / locks / hot-backups and so on. There's some rudimentary cluster-support for queries already in db4o, but they'll need definitively a more complex solution. Additionally they'll need some kind of blazing-fast cross-references between ObjectContainers. Objectivity does this very well (and is amazing fast connecting objects between different containers)."

https://na2.salesforce.com/00T4000000WOZuE



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.