[Info-vax] Distributed Applications, Hashgraph, Automation

[Kerry Main]

> -----Original Message-----
> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf Of
> Phillip Helbig undress to reply via Info-vax
> Sent: February 15, 2018 6:29 AM
> To: info-vax at rbnsn.com
> Cc: Phillip Helbig undress to reply <helbig at asclothestro.multivax.de>
> Subject: Re: [Info-vax] Distributed Applications, Hashgraph,
Automation
> 
> In article <mailman.1.1518663581.18116.info-
> vax_rbnsn.com at rbnsn.com>,
> "Kerry Main" <kemain.nospam at gmail.com> writes:
> 
> > Regardless of the OS platform, there is really only 2 types of
> > clustering architectures:
> >
> > 1. Shared disk (OpenVMS, Linux/GFS ,z/OS, others)
> > 2. Shared nothing (OpenVMS, Linux. Windows, *NIX, Non-Stop,
> others)
> 
> Shared disk and shared nothing.
> 
> > I like the analogy that compares the shared nothing model (Windows,
> > Linux, OpenVMS) to a dragster and the shared everything model
> > (Linux/GFS, OpenVMS, Z/OS) to a Ferrari.  In a quarter mile race on
a
> > track, the dragster will win hands down every time. In a race on
normal
> > streets, the Ferrari will win every time.
> 
> Shared everything and shared nothing.
> 

Just to clarify - 

While the OpenVMS community refer to its clustering arch as shared
everything, the industry term for the same thing is shared disk.

In both cases, one could refer to these as differing strategies to share
data between multiple systems. There are pro's and con's.  

Another good extract from the link 
<
http://www.benstopford.com/2009/11/24/understanding-the-shared-nothing-a
rchitecture/>

" Shared Disk Architectures are write-limited where multiple writer
nodes must coordinate their locks around the cluster. Shared Nothing
Architectures are write limited where writes span multiple partitions
necessitating a distributed two phase commit."

So, in terms of the new crypto currency considerations, the real
question is "regardless of the OS platform, and keeping in mind that the
network is by far the biggest contributor to overall "solution" latency,
which data sharing strategy (shared disk or shared nothing) is a better
approach a crypto currency solution?

The second question wold then be "given the answer to the first
question, what OS platform is better suited and has proven itself as a
solid implementation of the strategy decided on in question 1".

[hint - try not to let OS religion drive the decision on answer to Q1]


Regards,

Kerry Main
Kerry dot main at starkgaming dot com