Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Cleve Gibbon on Jul 25, 2008
David started by stepping through the key features of Morph AppSpace:
The top "feature" is that we provide an end-to-end managed service for web applications, changing the paradigm around hosting. Morph AppSpace combines technology, processes and people together into an on-demand service for a web application. Developers deploy their application to a Morph AppSpace and it is live to the world in a matter of minutes. No longer do developers need to think in terms of servers or software stacks, they think in terms of application delivery.Looking a layer deeper into the features I would say that what makes us special is that we provide a fault tolerant environment based on standards and open source technologies. We provide web-based interfaces that provide integrated features like web statistics and performance statistics that let the developer better understand how their application is behaving. We also have a unique approach to data protection where we keep data safe by continuously streaming it to physical storage.
Morph AppSpace is not an application programming model for delivering scalable web apps. Engineers at Morph AppSpace reiterated that the platform is programming model agnostic. Developers are still responsible for knowing how to design, build and assemble scalable web applications. Once the web application has been packaged, the platform provides tools to assist in the downstream activities associated with deploying and managing it within the cloud.
InfoQ asked David what the benefits are for an organisation thinking of using Morph AppSpace:
The main benefit is taking advantage of Morph's expertise in running and managing a world-class web application environment. By deploying applications to the Morph AppSpace, companies can eliminate the need for servers, web hosts, consultants/employees to do system administration tasks (like setting up operating systems, architecting high availability or dealing with server level security). Each Morph AppSpace is like having an external IT department that is solely focused on keeping the web platform up-to-date and running at optimal levels.
Also, given that hosting is a crowded marketplace, how does Morph AppSpace compare to other companies such as Heroku, RightScale, Mosso:
Each of these companies you mention targets a different need. From what we have seen with Heroku, they are still in the early exploratory phases with their solution. They have a beta version of an online web editing tool for code development and the ability to deploy the application created there to a pre-configured web stack running on Amazon EC2 where it currently mingles with other applications.Rightscale is what we consider a Cloud infrastructure management company. They provide the tools necessary to manage a farm of servers in the Cloud. It is still up to the user of RightScale to figure out how they are going to use those servers, install software and manage the entire environment. Rightscale products streamline the process of bringing new servers online and configuring those servers with pre-defined packages or scripts to load software or data.
Mosso is an advancement on hosting, leveraging features of the cloud. The overall paradigm is still based on hosting web sites, yet Mosso handles several of the system administration tasks for the user. This is a different view of the world than we take at Morph. Our focus is on web applications and the infrastructure needed to properly run and manage that application.
Morph AppSpace removes the need for system administration, add statistics and provides prebuilt stacks for specific development scenarios. However, exactly what value add does Morph AppSpace when contrasted with the services offered by EC2. David summarised with the following:
Amazon EC2 provides a developer with servers while Morph provides the developer with an application environment.
He continued with the following transportation analogy:
Amazon EC2 is like getting an engine, a set of wheels and a chassis. Yes, you could assemble these into transportation, but do you really want to spend your time doing that? And do you have the skills to do it? On the other hand, Morph is a car. You just get in and drive to work. Now apply this to applications.
At the heart of the platform is the Morph AppSpace cube. A cube's application stack is comprised of the Jetty web container that has been pre-configured with 256Mb RAM. Out-of-the-box support for MySql, PostgreSQL and email means that these jars are baked into the application stack. However, the ability to fine-tune the JVM is not there yet. Moreover, a cube's application stack is pretty much closed to any sort of modification.
When asked what's next for Morph App, David responded:
We continue to work to simplify the environment and integrate with as many 3rd party development tools as possible (currently we have plug ins for deploying via Eclipse, Maven and Ant). We have just added MySQL support along with the availability of Java/Grails environment.
Morph AppSpace has a subscription-based pricing model. There are eight different types of subscriptions where price varies depending on the number of cubes, size of database, required bandwidth and file storage. Subscription payments can either be made daily or monthly.
Modeling Your Cloud Services Brokerage
Getting Started with Stratos - an Open Source Cloud Platform
18 agile and lean practices for effective software development governance
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
No comments
Watch Thread Reply