IWETHEY v. 0.3.0 | TODO
1,095 registered users | 1 active user | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New mmm kay
They are all a continuum, but generally you can only get two at a time.

Consistency means that whatever data you have is never stale. It is never wrong. You relax this by saying it is never more than one version out of date or it is never more than 2 minutes old.

Availability means you always have data at your fingertips. You never have to wait long for it. Fetches return immediately with what you expect them to. The data may or may not be current. You relax this by allowing things like "Data is locked by other user - please come back tomorrow" states.

Reliability or Scalability implies that the system is always up - it can scale with just the addition of hardware and is capable of withstanding component/peer failure. Relaxing this means using something like a central lock server to manage data consistency introduces a single point of failure that will take down your system. Doing this will cause to to relax availability.

Here's a great talk about this stuff by Werner Vogels. [link|http://www.itconversations.com/shows/detail459.html|http://www.itconvers...ws/detail459.html]





[link|http://www.blackbagops.net|Black Bag Operations Log]

[link|http://www.objectiveclips.com|Artificial Intelligence]

[link|http://www.badpage.info/seaside/html|Scrutinizer]
New That's what I thought, for the most part.
So consistency, then availability, then reliability.

One process per instance, reading all of the data into RAM, then with lazy writes to persistent storage fits the above, I think. Enough of the scalability can still be there, I think, for purposes of the example problem we're discussing, since each instance gets its own process.

Werner's blog won't load right now; I'll check it out again later.
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
New Or how about we do this:
Let's talk about the solutions three ways, one for each of the tripod being dropped.
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
     Programming and design experiment - (admin) - (27)
         Yes, or Icon, Wade... ;-) -NT - (admin) - (1)
             I do most of my programming in PHP these days. - (static)
         This sounds familiar. - (static) - (5)
             Re: This sounds familiar. - (admin) - (4)
                 We're back to a scalability layer. - (static) - (3)
                     You can do that with PEAR - (drewk) - (1)
                         ADODB has a reputation. - (static)
                     Re: We're back to a scalability layer. - (admin)
         A few ideas - (admin) - (6)
             How critical is update ordering? - (drewk) - (5)
                 Critical. - (admin) - (4)
                     That's could be really hard. - (static) - (3)
                         One reason why I lean towards all-in-memory - (admin) - (2)
                             Doable from a database as well... - (ChrisR) - (1)
                                 I didn't say it wasn't doable. - (admin)
         Consistency, Availability, Reliability - (tuberculosis) - (4)
             Define your terms. - (admin) - (3)
                 mmm kay - (tuberculosis) - (2)
                     That's what I thought, for the most part. - (admin)
                     Or how about we do this: - (admin)
         Have you looked at the O'Reilly database war stories? - (tonytib) - (4)
             Yes, I've seen those before. - (admin) - (3)
                 I'm really starting to think there's something to my idea - (drewk) - (2)
                     Isn't that what SQLite is sorta trying to solve? - (static) - (1)
                         It's a solution to a specific problem - (drewk)
         XBase, of course. - (pwhysall) - (1)
             I heard that -NT - (tablizer)

Sorry, what? I wasn't listening. I was fantasizing that I was far away, very alone, and reading a book.
48 ms