[Info-vax] Distributed Applications, Hashgraph, Automation

[Kerry Main]

> -----Original Message-----
> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf Of IanD
> via Info-vax
> Sent: February 20, 2018 2:57 PM
> To: info-vax at rbnsn.com
> Cc: IanD <iloveopenvms at gmail.com>
> Subject: Re: [Info-vax] Distributed Applications, Hashgraph, Automation
> 
> On Thursday, February 15, 2018 at 6:53:40 AM UTC+11, Arne Vajhøj
> wrote:
> > On 2/14/2018 1:52 PM, IanD wrote:
> > > This is indeed interesting news
> > >
> > > I know it was posted a while ago but I just saw it
> > >
> > > https://www.swirlds.com/vms-software-selects-swirlds-hashgraph-
> as-platform-to-build-secure-distributed-applications/
> >
> > > I wonder if Hashgraph has the ability to ultimately replace cluster
> > > traffic on OpenVMS? It's supposed to scale to I think 200K
> > > transactions per second, according to the glossy brouchers at least
> > I think it is a business application thing not an OS thing.
> >
> > [application clusters are in many ways doing the same as OS clusters,
> > but ...]
> >
> > After all it is a J thing.
> >
> > :-)
> >
> > Arne
> 
> Yes, it is an application thing
> 
> But the throughout and number of nodes possible was the interesting
> point to me
> 
> I thought if it could be adapted (and I have no idea if it can be, I've only
> watched some video's etc and read the glossy brochures) then it might
> be a mechanism to allow scaling of VMS clusters beyond the 96 to a few
> thousand, which I believe Hashgraph can scale to
> 

Lets not forget that OpenVMS can be deployed in a shared nothing environment just as easily as Windows or Linux.

All of the locking and data partitioning In a shared nothing "cluster" is done at the app / db level, so why could this not also be done with OpenVMS?

Yes, the pricing, tcpip stack and file system on OpenVMS needs to be updated, but these major changes are cooking for release with OpenVMS X86. 

> The other point that Hoff keeps raising and I agreed wholeheartedly with
> is around the use of LDAP to replace VMS UAF etc
>

The right approach would be to adopt a local/domain model similar to Windows. 

Windows has the concept of a local account (sysuaf) or an AD domain account (LDAP)

Regards,

Kerry Main
Kerry dot main at starkgaming dot com