Thin network-based resource integration
A legacy resource is virtualized as a virtualized resource defined by features and capabilities set by an individual through a front-end user interface. Access rules are set on the virtualized resource based on the features and capabilities. When an access is requested to the virtualized resource, the corresponding access rules are enforced. Assuming there is no violation in the access rules, virtualized legacy resource services are overlaid on legacy resource services to cause the legacy resource services to perform any needed access operations on the corresponding legacy resource associated with the virtualized resource without changing any workflows processed by the legacy resource services.
1 . A method, comprising:
expanding a first definition for first capabilities of a legacy resource in a second definition for second capabilities of a virtual resource;
assigning access rules to the virtual resource based on the second definition and the second capabilities;
linking the virtual resource to a legacy resource service associated with accessing the legacy resource;
enforcing the access rules during a first access operation on the virtual resource; and
causing the legacy resource service to perform a second access operation on the legacy resource based on performing the first access operation on the virtual resource maintaining the legacy resource in agreement with the first access operation by the legacy resource service performing the second access operation on the legacy resource, wherein the virtual resource includes an alias identifier that is in a same format and of a same length as a conventional account associated with financial accounts, loyalty accounts, social media accounts, or service accounts;
wherein the virtual resource is overlayed on the legacy resource and the access rules are custom-defined rules processed through a thin network-based service.
2 . The method of claim 1 , wherein expanding further includes receiving a virtual resource type from a user through a user interface, presenting available attributes to the user through the user interface based on the virtual resource type, obtaining attribute selections from the available attributes provided by the user through the user interface, and generating the second definition based on the virtual resource type and the attribute selections.
3 . The method of claim 2 , wherein assigning further includes generating an alias identifier for the second definition and linking the alias identifier to the user and the second definition associated with the virtual resource.
4 . The method of claim 3 further comprising, providing the alias identifier to the user through the user interface.
5 . The method of claim 4 , wherein linking further includes receiving a legacy resource identifier for the legacy resource from the user through the user interface and identifying the legacy resource service based on the legacy resource identifier.
6 . The method of claim 1 , wherein enforcing further includes receiving an alias identifier for the virtual resource, access details, and the first access operation from a workflow that is associated with a transaction being processed that references the alias identifier for the virtual resource.
7 . The method of claim 6 , wherein receiving further includes receiving the alias identifier, the access details, and the first access operation on a communication port being monitored for a virtual resource type assigned to the virtual resource.
8 . The method of claim 7 , wherein enforcing further includes enforcing additional access rules against the first access operation based on the communication port.
9 . The method of claim 1 , wherein causing further includes:
processing an application programming interface (API) to provide a legacy identifier for the legacy resource, access details for the second access operation, and the second access operation to the legacy resource service causing the legacy resource service to perform the second access operation on the legacy resource using the access details.
10 . The method of claim 9 , wherein processing further includes:
providing a second legacy resource identifier for a second legacy resource in the access details based on the second access operation.
11 . The method of claim 10 further comprising, providing at least one confirmation that the legacy resource service completed processing the second access operation on the legacy resource upon notification received from the legacy resource service through the API.
12 . The method of claim 1 , wherein causing further includes updating a ledger maintained for the virtual resource based on the first access operation and the second access operation.
13 . A system, comprising:
a server comprising at least one processor and a non-transitory computer-readable storage medium;
the non-transitory computer-readable storage medium comprising server executable instructions;
the server executable instructions, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
providing a front-end interface to define capabilities of at least one virtual resource overlaid on at least one legacy resource;
assigning customized access rules to the at least one virtual resource based on user-defined input provided through the front-end interface;
enforcing the customized access rules during first access operations that reference the at least one virtual resource;
causing a legacy resource service associated with the at least one legacy resource to perform second access operations against the at least one legacy resource based on processing the first access operations against the at least one virtual resource; and
maintaining an updated ledger that balances the first access operations performed on the at least one virtual resource with the second access operations performed on the at least one legacy resource by the legacy resource service, wherein the at least one virtual resource includes an alias identifier that is in a same format and of a same length as a conventional account associated with financial accounts, loyalty accounts, social media accounts, or service accounts;
wherein a virtual resource service overlays the legacy resource service and a thin network-based resource integration service supports enhanced resource attributes, resource aliases, pools of resources, and multiple resource owners of a single virtualized resource.
14 . The system of claim 13 , wherein the at least one virtual resource includes a single virtual resource and the at least one legacy resource includes two or more legacy resources.