Colonization of transactional data based upon geography

Abstract

An example computer system for colonizing transactions can include: one or more processors; and non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to: receive a transaction initiated by an originator; automatically route the transaction to a colony based upon a context packet associated with the transaction; and store data associated with the transaction in the colony; wherein the colony satisfies regulatory requirements of a geographic area associated with the transaction.

What is claimed is: 
     
         1 . A computer system for colonizing transactions, comprising:
 one or more processors; and   non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to:
 receive a transaction having a transaction type initiated by an originator; 
 segment a colony stored within one or more databases into data streets, with the data streets being storage areas corresponding to different transaction types; 
 automatically route the transaction to a specific data street of the colony based upon a context packet associated with the transaction; 
 store data associated with the transaction in the specific data street of the colony; 
 crawl the colony within the one or more databases to determine an efficiency of the colony; and 
 divide the colony into two or more new colonies when the colony is too large, based upon the data streets in the colony, to accommodate increases in data in the colony while maintaining the efficiency for the one or more databases; 
 wherein the colony satisfies regulatory requirements of a geographic area associated with the transaction, and 
 wherein the specific data street corresponds to the transaction type of the transaction. 
   
     
     
         2 . The computer system of  claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to:
 generate multiple colonies at different geographic locations; and   store the data associated with the transaction in one of the multiple colonies.   
     
     
         3 . The computer system of  claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to generate a new colony when the regulatory requirements change. 
     
     
         4 . The computer system of  claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to destruct the colony when the regulatory requirements change. 
     
     
         5 . The computer system of  claim 1 , wherein the context packet includes a location of the originator. 
     
     
         6 . The computer system of  claim 5 , wherein the geographic area is the location of the originator. 
     
     
         7 . The computer system of  claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to identify a type and a location of the transaction from the context packet. 
     
     
         8 . The computer system of  claim 7 , wherein the type and the location of the transaction are used to select a data street within the colony. 
     
     
         9 . A method for colonizing transactions, comprising:
 receiving a transaction having a transaction type initiated by an originator;   segmenting a colony stored within one or more databases into data streets, with the data streets being storage areas corresponding to different transaction types;   automatically routing the transaction to a specific data street of the colony based upon a context packet associated with the transaction;   storing data associated with the transaction in the colony;   crawling the colony within the one or more databases to determine an efficiency of the colony; and   dividing the colony into two or more new colonies when the colony is too large, based upon the data streets in the colony, to accommodate increases in data in the colony while maintaining the efficiency for the one or more databases;   wherein the colony satisfies regulatory requirements of a geographic area associated with the transaction; and   wherein the specific data street corresponds to the transaction type of the transaction.   
     
     
         10 . The method of  claim 9 , further comprising:
 generating multiple colonies at different geographic locations; and   storing the data associated with the transaction in one of the multiple colonies.   
     
     
         11 . The method of  claim 9 , further comprising generating a new colony when the regulatory requirements change. 
     
     
         12 . The method of  claim 9 , further comprising destructing the colony when the regulatory requirements change. 
     
     
         13 . The method of  claim 9 , wherein the context packet includes a location of the originator. 
     
     
         14 . The method of  claim 13 , wherein the geographic area is the location of the originator. 
     
     
         15 . The method of  claim 9 , further comprising identifying a type and a location of the transaction from the context packet. 
     
     
         16 . The method of  claim 15 , wherein the type and the location of the transaction are used to select a data street within the colony.