TECHNICAL FIELD

This application generally relates to membership access management, and more particularly, membership access management of a database.

BACKGROUND

A centralized database stores and maintains data in one single database (e.g., database server) at one location. This location is often a central computer, for example, a desktop central processing unit (CPU), a server CPU, or a mainframe computer. Information stored on a centralized database is typically accessible from multiple different points. Multiple users or client workstations can work simultaneously on the centralized database, for example, based on a client/server configuration. A centralized database is easy to manage, maintain, and control, especially for purposes of security because of its single location. Within a centralized database, data redundancy is minimized as a single storing place of all data also implies that a given set of data only has one primary record.

However, a centralized database suffers from significant drawbacks. For example, a centralized database has a single point of failure. In particular, if there are no fault-tolerance considerations and a hardware failure occurs (for example a hardware, firmware, and/or a software failure), all data within the database is lost and work of all users is interrupted. In addition, centralized databases are highly dependent on network connectivity. As a result, the slower the connection, the amount of time needed for each database access is increased. Another drawback is the occurrence of bottlenecks when a centralized database experiences high traffic due to a single location. Furthermore, a centralized database provides limited access to data because only one copy of the data is maintained by the database. As a result, multiple devices cannot access the same piece of data at the same time without creating significant problems or risk overwriting stored data. Furthermore, because a database storage system has minimal to no data redundancy, data that is unexpectedly lost is very difficult to retrieve other than through manual operation from back-up storage.

Conventionally, a centralized database is limited by its ability to manage membership access and to offer certain members access to only information pertaining to their organization and related organizations. As such, what is needed is a solution to overcome these significant drawbacks.

SUMMARY

One example embodiment may provide a system that includes a plurality of member devices and corresponding member profiles identifying previously identified members and one or more new members of a permissioned database, and a computing node configured to perform one or more of identify a new member (M1) to the permissioned database, create a new group including the new member and one or more previously identified members (MP), modify a world state of the permission database to identify a set of members in the new group with access to the permissioned database, and responsive to the new member (M1) being identified, create a new entry (TX1) to the permissioned database using an encryption key (K1) associated with the new member (M1).

Another example embodiment may include a method that includes one or more of identifying a new member (M1) to a permissioned database, creating a new group including the new member and one or more previously identified members (MP), modifying a world state of the permissioned database to identify a set of members in the new group with access to the permissioned database, and responsive to the new member (M1) being identified, creating a new entry (TX1) to the permissioned database using an encryption key (K1) associated with the new member (M1).

Still another example embodiment may include one or more of a non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform identifying a new member (M1) to a permissioned database, creating a new group including the new member and one or more previously identified members (MP), modifying a world state of the permissioned database to identify a set of members in the new group with access to the permissioned database, and responsive to the new member (M1) being identified, creating a new entry (TX1) to the permissioned database using an encryption key (K1) associated with the new member (M1).

