In AppScale, we call each App Engine application instance an AppServer. It’s the unit we use to scale the application. Applications need at least one AppServer running to serve requests. Adding more AppServers increases application performance and redundancy.
AppScale 3.1 saw the introduction of the Azure agent in a beta capability. AppScale 3.2 brings a new and improved Azure agent which graduates to production ready our support of Azure. One of the main changes, was the introduction of Scale Sets in the agent code.
AppScale’s strong suit has been to support a wide range of resources, from clouds (public and private) to virtualized environments (virtualbox, kvm, docker, and more) to bare-metal (clusters and any resources the user has access to). Whenever there is a provisioning service, AppScale can take advantage of it to simplify resource management: for example, AWS, GCE, Azure, Euca, OpenStack all provide provisioning systems that AppScale can leverage to manage resources -- instances, network, disks.
I was pleasantly surprised last week when I read the latest Gartner report, Magic Quadrant for Enterprise Application Platform as a Service, Worldwide and found that our aPaaS, AppScale was prominently mentioned.
At AppScale Systems, we believe in the power of open source software to improve companies, expand access to technology and change lives.
It’s exciting to be partnering with Canonical / Ubuntu again as a member of their Charm Partner Program.