The systems and methods described herein dynamically allocate streams when restoring data from databases. In some embodiments, the system and methods restore data from a database by determining a number of streams to allocate to the database for restoring files of data from the database. The determined number of streams may be based on a total amount of data within the database, and/or may be based, at least in part, on the previous number of streams used during backup operations, in order to balance the benefit of allocating streams to a restoration of data with any detriments associated with changing the number of streams from the number used during previous backup operations.

System and methods are described for specifying, deploying, and using plugins during replication of a database. The method includes receiving a replication plugin service configuration specifying a plurality of plugins, getting a first database plugin specified by the replication plugin service configuration, getting one or more reader plugins specified by the replication plugin service configuration, deploying the first database plugin and the one or more reader plugins to a relay communicating with a source database, and getting data from the source database using the first database plugin and the one or more reader plugins.

A method includes capturing first data associated with a first packet flow originating from a first host using a first capture agent deployed at the first host to yield first flow data, capturing second data associated with a second packet flow originating from the first host from a second capture agent deployed outside of the first host to yield second flow data and comparing the first flow data and the second flow data to yield a difference. When the difference is above a threshold value, the method includes determining that a hidden process exists and corrective action can be taken.

Systems and methods receive an asset identification and one or more criterion to at least one of a locale, a market, a target, or an experiment and process a graph having a plurality of sub-graphs to define an asset having one or more desired variants. The asset is then published having the one or more desired variants. Multiple entities are represented as a single entity, which can be used for localization of the asset (e.g., image, video, custom data) or pages. By associating one entity (e.g., an image) across all variations of the entity, the needed storage space for the plurality of assets (e.g., images or videos) is reduced.

A method for compressing a first application file and second application file includes accessing the first and the second application files, the first application file being in a first language and the second application being in a second language and being a counterpart of the first application file, decompressing the first and second application files to access internal files for the first and the second application files, comparing one of the first internal files to one of the second internal files, upon determining that the first internal file is identical to the second internal file, copying one of the internal files to an output folder, and upon determining that the files are not identical, copying both of the internal files to the output folder, or executing a differencing procedure on the first and second internal files to identify differences between them, storing data about the differences in the output folder, and compressing the output folder into one output file.

Systems, methods, and computer-readable media for managing compromised sensors in multi-tiered virtualized environments. In some embodiments, a system can receive, from a first capturing agent deployed in a virtualization layer of a first device, data reports generated based on traffic captured by the first capturing agent. The system can also receive, from a second capturing agent deployed in a hardware layer of a second device, data reports generated based on traffic captured by the second capturing agent. Based on the data reports, the system can determine characteristics of the traffic captured by the first capturing agent and the second capturing agent. The system can then compare the characteristics to determine a multi-layer difference in traffic characteristics. Based on the multi-layer difference in traffic characteristics, the system can determine that the first capturing agent or the second capturing agent is in a faulty state.

A resource dependency system displays two dynamically interactive interfaces in a resource dependency user interface, a hierarchical resource repository and a dependency graph user interface. User interactions on each interface can dynamically update either interface. For example, a selection of a particular resource in the dependency graph user interface causes the system to update the dependency graph user interface to indicate the selection and also updates the hierarchical resource repository to navigate to the appropriate folder corresponding to the stored location of the selected resource. In another example, a selection of a particular resource in the hierarchical resource repository causes the system to update the hierarchical resource repository to indicate the selection and also updates the dependency graph user interface to display an updated graph, indicate the selection and, in some embodiments, focus on the selected resource by zooming into a portion of the graph.

A system includes a database containing database tables. The system also includes one or more processors configured to: (i) determine, for a software application, a set of the database tables containing information used by the software application; (ii) for an item associated with the software application, query the set of the database tables for entries related to the item, wherein the entries are in a first language; (iii) generate, for display, a representation of a first pane and a second pane, wherein the first pane contains the entries, and wherein the second pane contains data input elements for translations of the entries into a second language; (iv) transmit the representation; (v) receive data entered into the data input elements of the second pane; and (vi) store, in the set of the database tables, the data entered into the data input elements as a translation to the second language.

Database systems and related customization methods are provided. One exemplary method of modifying a database to support a new functionality involves receiving user input indicative of the new functionality from a client device coupled to a network, identifying existing customizations associated with a user of the client device in the database, determining a plurality of different solutions for implementing the new functionality based at least in part on the existing customizations associated with the user, providing a graphical user interface display at the client device including graphical indicia of the plurality of different solutions for implementing the new functionality, and in response to receiving indication of a selected solution of the plurality of different solutions from the client device, automatically instantiating a new customization corresponding to the selected solution in the database.

Technologies for detecting changes in a namespace using namespace enumeration endpoint response payloads are disclosed. A namespace is enumerated at a first time by retrieving response payloads containing metadata describing each location in the namespace from a namespace enumeration endpoint. Signatures are generated based on the response payloads and stored. To determine if changes were made to the namespace between the first time and a subsequent second time, metadata is retrieved from the namespace enumeration endpoint for the namespace at the second time and signatures are generated. Signatures generated at the first time are then compared to the signatures generated at the second time. If the signatures are different, the items in the location in the namespace changed between the first time and the second time. Changes occurring in a location of the namespace can then be identified based on the metadata obtained at the first and second times.