Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by James Cox on Feb 10, 2007
RailsConf 2007 registration is finally open, after months of waiting, submitting proposals and anxious waiting to see if we'll be able to snag a registration. This year, under the stewardship of O'Reilly, availability runs to 1200 seats, and registration opened a week ago. The show hasn't quite sold out yet, in contrast to last year when all tickets were gone in four hours. DHH is excited: being over half sold - "This makes RailsConf '07 the fastest selling conference that O' Reilly have been involved with".
This year's conference will be held from May 17th to May 20th in the spacious upper halls of the Oregon Conference in downtown Portland. The schedule is packed: expect to be entertained and meet all the names you've come to know from the mailing lists. The usual suspects will be keynoting, but look out for great talks from some of last year's favorites such as Ezra's Xen Deployment and Amy's Designer guide along with a whole host of first-time talks.
Our highlights include topics such as exploring rails in business, interaction with other libs and products. Of course, solid code discussion will not overlooked. Don't miss the rails way by Rails expert Jamis Buck. For those of you willing to remix and help improve this year's conference, O'Reilly are hosting a wiki for feedback and ad-hoc planning.
Current pricing (until March 19th) sets the registration fee at $745 with the tutorial day included, however there are a number of discounts available, including for alumni. The price rises to $995 if you register on the day of the conference, but don't expect there to be any tickets left!
In contrast to last year, many sponsorship opportunities are available too, up to $35,000 for the top spot. If this is a bit pricey for you, there are lower-cost options for vendors wishing to present in the exhibitor hall. A good amount of the profits will end up in the warchest of Ruby Central, a non-profit organization that helps to coordinate Ruby conferences.
Finally, if you didn't get accepted for a speaker slot this time around, don't worry: RejectConf will be back in full swing with InfoQ's own Obie Fernandez supplying cases of beer like last year.
The WebSphere Liberty Profile for Developers: An Introduction
RDBMS to NoSQL: Managing the Transition
Tools to unit test your JavaScript
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
No comments
Watch Thread Reply