System and method for developing, deploying, managing and monitoring a web application in a single environment

• US 8,954,553 B1
• Filed: 09/20/2009
• Issued: 02/10/2015
• Est. Priority Date: 11/04/2008
• Status: Active Grant

• Current Assignee: Appcelerator Incorporated (Axway Software SA)
• Original Assignee: Appcelerator Incorporated (Axway Software SA)
• Inventors: Colton, Paul, Sarid, Uri
• Primary Examiner(s): Dharia, Rupal
• Assistant Examiner(s): MCADAMS, BRAD
• Application Number:
  US12/563,159
• Time in Patent Office: 1,969 Days
• Field of Search: 709/203, 709/224, 709/226, 709/223
• US Class Current: 709/223
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 41/5083 wherein the managed service relates to web hosting
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1031 Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A system and method for developing, deploying, managing and monitoring a web application in a single environment is disclosed herein. The single environment is preferably an integrated development environment (“IDE”). The system and method preferably allows for deployment to a cloud provider, and preferably allows for use of Web resources from multiple cloud providers. One preferred IDE is the APTANA® STUDIO IDE.

Claims

1. A cloud management system for a web application that is operatively connected to a plurality of separate cloud providers, each of which comprises web resources for supporting the web application, the cloud management system comprising:

an application programming interface (“

API”

) comprising software program implemented class definitions to enable the cloud management system to remotely and automatically monitor the web application to determine if a current level of web resources is appropriate for the web application to perform within a predetermined performance range; and

a processor-based cloud manager component functionally coupled to the cloud management system through the API for accessing and providing a primary plurality of web resources to the web application from both a first of the cloud providers and a second of the cloud providers, wherein the cloud manager comprises a user interface configured to provide an operator with access to the cloud manager, wherein the cloud manager is loaded from a local data store and synchronizes a local data store model with a remote site manager model using a core model object that is configured for model elements to synchronize against a remote model representation to enable the cloud manager to provision, sync, and automatically provide scalability for the web application.

2. The cloud management system according to claim 1, wherein the core model object and a core group object fires events when a remote model changes, delete themselves from the remote model, and serializes to the local data store to enable an off-line mode, such that model change events are fired only for differences found between the local data store model and the site manager model.

3. The cloud management system according to claim 1, wherein the site manager model is implemented by a site manager configured to perform client implementation of site manager services, poll the site manager for notifications of events, and maintain and synchronize a project model with the site manager.

4. The cloud management system according to claim 1, wherein the cloud manager communicates with the first cloud provider through the API.

5. The cloud management system according to claim 4, wherein the cloud manager communicates with the second cloud provider through the API.

6. The cloud management system according to claim 1 being operatively connected to an internal IT site, the cloud manager being in communication with the internal IT site through the API.

7. The cloud management system according to claim 1, wherein the cloud manager is capable of changing the web application from a live state to a staging state.

8. The cloud management system according to claim 1, wherein the cloud manager varies the current level of web resources available to the web application according to a predetermined daily time schedule.

9. A method for developing, deploying, managing and monitoring a web application in a single environment, the method comprising:

developing a web application at a single integrated development environment utilizing a plurality of client-technology languages and a plurality of server-side languages, the single integrated development environment comprising a cloud manager configured to provision, sync, and automatically provide scalability for the web application, the cloud manager loaded from a local data store and synchronizing a local data store model with a remote site manager model using a core model object that is configured for model elements to synchronize against a remote model representation;

deploying the web application to a primary cloud provider having a primary plurality of web resources;

provisioning the web application with the primary plurality of web resources from the primary cloud provider by automatically accessing and providing the primary plurality of web resources from the primary cloud provider for the web application utilizing the cloud manager;

managing the web application within the single environment to determine if a current level of web resources is appropriate for the web application to perform within a predetermined performance range;

accessing and providing the primary plurality of web resources from the primary cloud provider to the web application;

accessing and providing a secondary plurality of web resources from at least one secondary cloud provider to the web application in addition to the primary plurality of web resources from the primary cloud provider; and

monitoring the performance of the web application from the single environment.

10. The method according to claim 9 wherein managing the web application comprises temporarily adding web resources from the secondary plurality of web resources during a time period of high demand for the web application.

11. The method according to claim 9 wherein the core model object and a core group object fires events when a remote model changes, delete themselves from the remote model, and serializes to the local data store to enable an off-line mode, such that model change events are fired only for differences found between the local data store model and the site manager model.

12. The method according to claim 9 wherein the site manager model is implemented by a site manager configured to perform client implementation of site manager services, poll the site manager for notifications of events, and maintain and synchronize a project model with the site manager.

13. The method according to claim 9 wherein a cloud manager accesses the primary cloud provider and the secondary cloud provider to obtain web resources for the web application.

14. A method for developing, deploying, managing and monitoring a web site in a single environment, the method comprising:

developing a web site in an integrated development environment;

deploying the web site from the integrated development environment to a primary cloud provider having a primary plurality of web resources;

provisioning the web site with the primary plurality of web resources from the primary cloud provider by automatically accessing and providing the primary plurality of web resources from the primary cloud provider for the web site utilizing a cloud manager configured to provision, sync, and automatically provide scalability for web applications provided by the web resources, the cloud manager loaded from a local data store and synchronizing a local data store model with a remote site manager model using a core model object that is configured for model elements to synchronize against a remote model representation;

allocating a secondary plurality of web resources from a secondary cloud provider to the web site in addition to the primary plurality of web resources from the primary cloud provider; and

monitoring and managing the web site from the integrated development environment to determine if a current level of web resources is appropriate for the web site to perform within a predetermined performance range.

15. The method according to claim 14 wherein developing the web site comprises using client-technology languages and server-side languages.

16. The method according to claim 15 wherein client-technology languages comprise HTML, CSS and JavaScript, and wherein server-side languages comprise PHP, Ruby, Python, Java and JavaScript.

17. The method according to claim 14 further comprising moving the web site from the cloud provider to a virtual server as a VMWARE image.

18. The method according to claim 14 wherein the core model object and a core group object fires events when a remote model changes, delete themselves from the remote model, and serializes to the local data store to enable an off-line mode, such that model change events are fired only for differences found between the local data store model and the site manager model.

19. The method according to claim 14 wherein the site manager model is implemented by a site manager configured to perform client implementation of site manager services, poll the site manager for notifications of events, and maintain and synchronize a project model with the site manager.