Criteria-based cost-efficient routing and deployment of metadata packages in an on-demand environment

Abstract

In accordance with embodiments, there are provided mechanisms and methods for facilitating criteria-based cost-efficient routing and deployment of metadata packages in an on-demand services environment according to one embodiment. In one embodiment and by way of example, a method comprises analyzing, by a metadata costing server computing device, characteristics of a metadata package awaiting deployment, where analyzing includes matching the characteristics with predefined criteria associated with deployment of metadata packages. The method may further include routing, by the metadata server, the metadata package for real-time deployment if the characteristics satisfy the criteria, where the real-time deployment allows for bypassing of message queues associated with standard deployment.

1 .- 20 . (canceled) 
     
     
         21 . A method comprising:
 determining, by a server, characteristics of a metadata package awaiting deployment;   ascertaining, by the server, routing guidelines corresponding to the metadata package based, at least in part, on the characteristics, the characteristics including one or more of: a deployment history of the metadata package, a size of the metadata package, an urgency associated with the metadata package, accrued credits, or preferences associated with the metadata package; and   routing, by the server, the metadata package for deployment according to the routing guidelines.   
     
     
         22 . The method of  claim 21 , wherein routing the metadata package is performed via real-time deployment, the characteristics indicating that the size of the metadata package is below a particular threshold. 
     
     
         23 . The method of  claim 22 , the particular threshold being defined by criteria maintained at one or more databases. 
     
     
         24 . The method of  claim 21 , wherein routing the metadata package is performed via standard deployment. 
     
     
         25 . The method of  claim 24 , the characteristics indicating that the size of the metadata package does not exceed a particular threshold. 
     
     
         26 . The method of  claim 24 , the characteristics failing to satisfy criteria for routing via real-time deployment. 
     
     
         27 . A non-transitory computer-readable storage medium having stored thereon instructions which, when executed, are configurable to cause a computing device to perform operations comprising:
 determining, by a server, characteristics of a metadata package awaiting deployment;   ascertaining, by the server, routing guidelines corresponding to the metadata package based, at least in part, on the characteristics, the characteristics including one or more of: a deployment history of the metadata package, a size of the metadata package, an urgency associated with the metadata package, accrued credits, or preferences associated with the metadata package; and   routing, by the server, the metadata package for deployment according to the routing guidelines.   
     
     
         28 . The non-transitory computer-readable storage medium of  claim 27 , wherein routing the metadata package is performed via real-time deployment, the characteristics indicating that the size of the metadata package is below a particular threshold. 
     
     
         29 . The non-transitory computer-readable storage medium of  claim 28 , the particular threshold being defined by criteria maintained at one or more databases. 
     
     
         30 . The non-transitory computer-readable storage medium of  claim 27 , wherein routing the metadata package is performed via standard deployment. 
     
     
         31 . The non-transitory computer-readable storage medium of  claim 30 , the characteristics indicating that the size of the metadata package does not exceed a particular threshold. 
     
     
         32 . The non-transitory computer-readable storage medium of  claim 30 , the characteristics failing to satisfy criteria for routing via real-time deployment. 
     
     
         33 . A system, comprising:
 one or more servers, the servers configurable to cause:   determining characteristics of a metadata package awaiting deployment;   ascertaining routing guidelines corresponding to the metadata package based, at least in part, on the characteristics, the characteristics including one or more of: a deployment history of the metadata package, a size of the metadata package, an urgency associated with the metadata package, accrued credits, or preferences associated with the metadata package; and   routing the metadata package for deployment according to the routing guidelines.   
     
     
         34 . The system of  claim 33 , wherein routing the metadata package is performed via real-time deployment. 
     
     
         35 . The system of  claim 34 , the characteristics indicating that the size of the metadata package is below a particular threshold. 
     
     
         36 . The system of  claim 33 , wherein routing the metadata package is performed via standard deployment. 
     
     
         37 . The system of  claim 36 , the characteristics indicating that the size of the metadata package does not exceed a particular threshold. 
     
     
         38 . The system of  claim 36 , the characteristics failing to satisfy criteria for routing via real-time deployment. 
     
     
         39 . The system of  claim 33 , wherein routing the metadata package is performed via real-time deployment, the characteristics indicating that the size of the metadata package is below a particular threshold defined by one or more criteria 
     
     
         40 . The method of  claim 39 , the criteria maintained at one or more databases.