> On 21 Nov 2023, at 8:20 pm, Scott Chapman > <000003fffd029d68-dmarc-requ...@listserv.ua.edu> wrote: > > I think the better question is why does EzNoSQL require RLS? Probably makes > it easier because they don't have to handle different sharing issues, but it > seems possible that some might be interested in using the EzNoSQL API from a > single task without sharing implications.
I haven’t used it but from reading the brief docs EzNoSQL is a z/OS implementation of a key/value JSON document store that uses VSAM KSDS as the store. It’s similar to MongoDB or SAP HANA in functionality which are both hugely popular on distributed systems. The marketing materials mention using Sysplex for consistency and performance. MongoDB, Aerospike, SAP HANA etc all have huge in-memory caches for scalability. EzNoSQL uses Sysplex services to implement a straight-through cache and persistent storage that can scale horizontally. IBM makes a point of stating that there are no programming requirements to handle eventual consistency which can be an issue with distributed systems that adhere to the CAP theorem. > Of course I don't know how interested people are in general in EzNoSQL. It looks decent but IBM needs to provide better documentation. > > Scott Chapman > > > On Mon, 20 Nov 2023 17:28:17 -0600, Peter Bishop <p.bis...@computer.org> > wrote: > >> Also, given it's just SMF data being used here, surely there's a way for >> z/OS to process that without VSAM RLS and EzNoSQL (?). Perhaps they are >> using "ported" code, i.e. not native to z/OS, for the AI inferencing part >> and hence must have EzNoSQL and thus VSAM RLS. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
