First look: Zend's PHP developer cloud

Zend Developer Cloud woos PHP developers with enterprise-grade development features, snapshots for easy recovery and project sharing, and promises of single-click cloud deployment

By Rick Grehan, InfoWorld |  Software, PHP, zend

When you consider the cloud, you typically imagine a realm of deployed, production applications. Zend Developer Cloud (ZDC) adds a twist: ZDC creates a place in the cloud where PHP-based applications can be developed for the cloud. No more developing locally, then deploying into the cloud -- ZDC pushes both into the ether.

If that were all it did, ZDC's utility would be questionable. However, it offers benefits that are not at first apparent, but warrant a closer look.

[ Also on InfoWorld: "Ruby clouds: Engine Yard vs. Heroku" and "4 Java clouds face off." | See if you can pass InfoWorld's programming IQ test, round 1 and programming IQ test, round 2. | Get software development news and insights from InfoWorld's Developer World newsletter. ]

At the time of this writing, the Zend Developer Cloud is still in beta. Interested developers can try it out at phpcloud.com. Access to ZDC -- during the beta phase -- is free. Anyone who takes advantage of this trial period will be able to keep a free account even after ZDC goes "live," which is anticipated sometime in early 2012. The live version will offer both free and paid-for accounts. Details of the differences between the two account types have yet to be officially specified, but the Zend engineers claim that anyone who has begun development work in the beta stage will lose none of that work when the system becomes publicly available.

Zend Developer Cloud: Zend Server and MySQL Zend Developer Cloud is hosted on Amazon Web Services, but hides the underlying Amazon infrastructure. Register with ZDC, and you are given a "container" -- a sandbox that hosts the execution of the applications you are developing. You can think of it as a virtual system, to which is allocated memory, disk, networking, and CPU resources. Specifically, a container is permitted approximately 300MB of memory, 500MB of disk space, and about 2TB per month of network bandwidth. The CPU allocation is specified in throughput consumed by database operations -- about 200MBps.


Originally published on InfoWorld |  Click here to read the original story.
Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Answers - Powered by ITworld

ITworld Answers helps you solve problems and share expertise. Ask a question or take a crack at answering the new questions below.

Ask a Question
randomness