Amazon Announces Lower Pricing for Route 53 DNS Service

Posted in: Cloud Computing

In an email to current customers today, Amazon announced that lower pricing will go into effect as of October 1st for their Route 53 DNS hosting service.

From the email:

We are excited to announce that effective October 1st we’re reducing prices for Amazon Route 53, Amazon Web Services’ reliable and scalable domain name service. Amazon Route 53 routes end users to your Internet applications by translating human readable names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. Effective October 1st, we’re cutting the price for each hosted zone from $1 per month to $0.50 per month for the first 25 zones, and then $0.10 per month for additional zones.

T8ADKXU5EC7P

Java PaaS Definition

Posted in: Cloud Computing, Enterprise Java

At a minimum, a Java PaaS solution provides a JVM based execution environment, built on top of production-ready cloud infrastructure, that allows for the easy deployment of applications, without having to provision or configure low-level system resources.

CQ Development Team Server “In A Box” (Updated)

Posted in: Enterprise Java

I just finished publishing a new machine image that includes improvements to integrate to the new repo.adobe.com Maven repository, and to also deploy CQ as a service so that it will startup and shutdown with the operating system.

Check the details here:

http://cqblueprints.com/xwiki/bin/view/Blue+Prints/CQ+Development+Team+Server+%22In+A+Box%22

Using Nexus as a Maven Repository for CQ Team Development (Updated)

Posted in: Enterprise Java

I just finished doing a major update to the CQ Blueprints page about using Nexus as a Maven Repository for CQ development. The Blueprint now demonstrates how to make use of the repo.adobe.com repository that Adobe has recently made available.

Customers who wisely choose Maven as their build tool should setup their own Maven Repositories and configure them to proxy the repo.adobe.com repository to provide access to the CQ related artifacts for your team. Some possibly outdated documentation on the Day/Adobe sites recommends installing and using Apache Archiva as your local repository. However, since Nexus is now being used actively to manage the Maven Central repository it has become the defacto standard for Maven Repository management tools. As a result, we recommend the use of Nexus over any other Maven Repository management tools, including Archiva.

via Using Nexus as a Maven Repository for CQ Team Development Blue Prints.Using Nexus as a Maven Repository for CQ Team Development – XWiki.

Google Attempts Some Damage Control For App Engine Price Changes

Posted in: Cloud Computing, Enterprise Java

We understand that the new rates surprised some of you. We’ve been listening closely to your feedback, and we wanted to share an update on the changes we’re making to help ensure you have an accurate picture of how the new pricing will affect your app. Although prices will increase, we’re confident that you’ll find App Engine still provides great value.

via Google App Engine Blog: A few adjustments to App Engine’s upcoming pricing changes.

Java PaaS Vendor Survey – September 2011 (YouTube)

Posted in: Cloud Computing, Enterprise Java

CQ Development Team Server “In A Box”

Posted in: System Administration

Just wrapped up a project with the Headwire team to create an example server environment for getting up and running with a new CQ project quickly. The server has all of the elements needed for a CQ development team like Subversion, Nexus and Jenkins already installed, configured and integrated. There are also instructions for setting up your CQ environment, including deploying the CQ binaries into Nexus and making them available to your Maven builds.

The server is packaged as an Open Virtualization Archive file, so you should be able to import it into most virtualization tools (VirtualBox, VMware etc).

Check out the documentation here:

http://www.cqblueprints.com/xwiki/bin/view/Blue+Prints/CQ+Development+Team+Server+%22In+A+Box%22

Using Nexus as a Maven Repository for Adobe CQ Team Development

Posted in: Enterprise Java

I just finished writing another Blueprint over on the CQ Blueprints site. This time I talk about how to go about setting up and using Nexus as your team’s Maven Repository when working with Adobe CQ (now Adobe ADEP / CEM).

Check it out here: http://www.cqblueprints.com/xwiki/bin/view/Blue+Prints/Using+Nexus+as+a+Maven+Repository+for+CQ+Team+Development

How To Easily Deploy Pre-Packaged Maven Artifacts

Posted in: Enterprise Java

The Maven deploy:deploy-file goal is very useful for deploying JARs (and other artifacts) that have not been mavenized, to your own repository. It allows you to pass Maven coordinates and other Maven related meta data on the command line so that the artifact ends up in the right spot in your repository and has at least the bare minimum of Maven meta data associated with it to make it useful. Unfortunately, one less common scenario it does not currently handle is deploying an already mavenized artifact to a repository. I recently ran into this exact issue while doing some work for a client, so I put together a script to bridge the gap.

Continue reading »

Amazon Web Services: 15 Ways It Makes Cloud App Development Easier

Posted in: Cloud Computing

Amazon Web Services (AWS) provides one of the most popular infrastructure as a service (IaaS) cloud platforms around. Since 2006, AWS has provided companies of all sizes with an infrastructure Web services platform in the cloud. With AWS, users can requisition compute power, storage and other services, and gain access to a suite of elastic IT infrastructure services as their needs increase or decrease. In addition, AWS gives developers the flexibility to choose whichever development platform or programming model makes the most sense for the problems they’re trying to solve. Users pay only for what they use, with no up-front expenses or long-term commitments, which makes AWS a cost-effective way to deliver applications to customers and clients. AWS also allows users to take advantage of Amazon.com’s global computing infrastructure that is the backbone of Amazon.com’s multibillion-dollar retail business and transactional enterprise—the scalable, reliable and secure distributed computing infrastructure that has been honed for more than a decade. Although AWS does not have a specific developer program, the company continues to offer new services and offerings that benefit developers. These include Amazon CloudFront, Amazon Elastic Compute Cloud (Amazon EC2), Amazon Relational Database Service and Amazon Elastic Beanstalk. Amazon EC2 celebrated its fifth birthday on Aug. 25. Here, eWEEK looks at the ways AWS makes it easier for developers as they move to the cloud.

via Amazon Web Services: 15 Ways It Makes Cloud App Development Easier – Cloud Computing – News & Reviews – eWeek.com.