Abstract: An approach is described for providing unified technological stack management (e.g., via a global storage instance) where metadata is delocalized from storage nodes. The approach includes creating a global storage instance, wherein the global storage instance contains metadata for a storage layer including a plurality of storage nodes, and wherein the global storage instance is delocalized from the plurality of storage nodes. The approach also includes receiving a database operation request from an operating system layer. The approach further includes mediating the database operation request between the operating system layer and the storage layer using the global storage instance.

Abstract: An approach is described for providing unified technological stack management (e.g., via a global storage instance) where metadata is delocalized from storage nodes. The approach includes creating a global storage instance, wherein the global storage instance contains metadata for a storage layer including a plurality of storage nodes, and wherein the global storage instance is delocalized from the plurality of storage nodes. The approach also includes receiving a database operation request from an operating system layer. The approach further includes mediating the database operation request between the operating system layer and the storage layer using the global storage instance.

Abstract: An approach is described for providing unified technological stack management (e.g., via a global storage instance) where metadata is delocalized from storage nodes. The approach includes creating a global storage instance, wherein the global storage instance contains metadata for a storage layer including a plurality of storage nodes, and wherein the global storage instance is delocalized from the plurality of storage nodes. The approach also includes receiving a database operation request from an operating system layer. The approach further includes mediating the database operation request between the operating system layer and the storage layer using the global storage instance.

Abstract: An approach is described for providing unified technological stack management (e.g., via a global storage instance) where metadata is delocalized from storage nodes. The approach includes creating a global storage instance, wherein the global storage instance contains metadata for a storage layer including a plurality of storage nodes, and wherein the global storage instance is delocalized from the plurality of storage nodes. The approach also includes receiving a database operation request from an operating system layer. The approach further includes mediating the database operation request between the operating system layer and the storage layer using the global storage instance.

Abstract: A database is replicated to other systems using multisite table(s) and associated replication trigger logic. Each system includes a main table, multisite table(s) and replication trigger logic. A multisite table corresponds to a main table of another system. When a main table of a system is changed, in response to an input, the system generates and sends replication transactions to the other systems for changing main tables in the other systems. In accordance with the change specified in the replication transaction, the multisite tables are modified. In each system, the replication trigger logic determines whether or not to replicate the change specified in the replication transaction to the main table of the each system, upon application of the replication trigger logic to the replication transaction. The change specified in the replication transaction may relate to inserting, deleting, or updating a record in the main table.

Abstract: A user is allowed to access any of a number of domains associated with an enterprise using a credential for any one of the domains. An exemplary method includes steps of receiving, from a user and at a first domain of the enterprise, a user identification and a password; determining, at the first domain, whether the user identification is associated with the first domain; and upon determination that the user identification is not associated with the first domain, determining, at the first domain, whether the user identification is associated with a second domain of the enterprise. The user identification and the password are authenticated at the first domain, upon determination that the user identification is associated with the second domain. Upon successful authentication, the user is enabled to access the second domain of the enterprise. The user identification does not need to include a character directly reflecting a domain name.