Abstract: Systems and methods are disclosed for extracting a topology for an installation of a plurality of software components. The topology may be extracted from instantiating instructions for the components of the installation such as an application manifest, manifest tree, configuration scripts, source code, and the like. One of a plurality of rendering engines generates one of a plurality of representations of the topology. Status data for the components may be collected and visually represented on the graphical representation of the topology. Examples of representations include a network topology, a release pipeline graph, a service architecture, and a state machine graph. The status of the topology may be updated in realtime as status information is output by the installation.

Abstract: Websites, including supporting databases, are updated with little or no downtime. In one aspect, a database is replicated prior to updating, so that updates can be performed on one copy while the other remains operational. In another aspect, the data remains in one location while an application programming interface for interacting with the data using new software code is introduced. Another application programming interface remains operational while the update is taking place. Public and private synonyms are used to direct web traffic to the appropriate application programming interface during the update process.

Abstract: Websites, including supporting databases, are updated with little or no downtime. In one aspect, a database is replicated prior to updating, so that updates can be performed on one copy while the other remains operational. In another aspect, the data remains in one location while an application programming interface for interacting with the data using new software code is introduced. Another application programming interface remains operational while the update is taking place. Public and private synonyms are used to direct web traffic to the appropriate application programming interface during the update process.

Abstract: Systems and methods are disclosed for extracting a topology for an installation of a plurality of software components. The topology may be extracted from instantiating instructions for the components of the installation such as an application manifest, manifest tree, configuration scripts, source code, and the like. One of a plurality of rendering engines generates one of a plurality of representations of the topology. Status data for the components may be collected and visually represented on the graphical representation of the topology. Examples of representations include a network topology, a release pipeline graph, a service architecture, and a state machine graph. The status of the topology may be updated in realtime as status information is output by the installation.

Abstract: Websites, including supporting databases, are updated with little or no downtime. In one aspect, a database is replicated prior to updating, so that updates can be performed on one copy while the other remains operational. In another aspect, the data remains in one location while an application programming interface for interacting with the data using new software code is introduced. Another application programming interface remains operational while the update is taking place. Public and private synonyms are used to direct web traffic to the appropriate application programming interface during the update process.

Abstract: An improved data access layer (DAL) architecture enables database connection pooling or multiplexing across machine boundaries. Drivers installed at web servers communicate with servers in a DAL. The DAL servers present a virtual database to the web servers, and the DAL servers in turn open connections to a set of physical databases. DAL servers are able to recycle connections that are no longer needed, or to move available connections from one DAL server to another, so as to provide improved efficiency in connection management, burst management, and peak load management. Scalability is thereby improved, and more efficient use of system resources is facilitated.

Abstract: An improved data access layer (DAL) architecture enables database connection pooling or multiplexing across machine boundaries. Drivers installed at web servers communicate with servers in a DAL. The DAL servers present a virtual database to the web servers, and the DAL servers in turn open connections to a set of physical databases. DAL servers are able to recycle connections that are no longer needed, or to move available connections from one DAL server to another, so as to provide improved efficiency in connection management, burst management, and peak load management. Scalability is thereby improved, and more efficient use of system resources is facilitated.

Abstract: An improved data access layer (DAL) architecture enables database connection pooling or multiplexing across machine boundaries. Drivers installed at web servers communicate with servers in a DAL. The DAL servers present a virtual database to the web servers, and the DAL servers in turn open connections to a set of physical databases. DAL servers are able to recycle connections that are no longer needed, or to move available connections from one DAL server to another, so as to provide improved efficiency in connection management, burst management, and peak load management. Scalability is thereby improved, and more efficient use of system resources is facilitated.