New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Jul 19, 2010
Rackspace has opened its cloud computing platform source code under Apache 2.0 license as part of OpenStack initiative. NASA is contributing with technology powering NASA Nebula Cloud Platform.
Rackspace has announced the creation of OpenStack Project, an initiative aiming to become the open source solution for cloud computing. The first component of the platform is Object Storage based on Rackspace’s Cloud Files source code, while a second component, Compute, based on NASA Nebula’s computing engine and Rackspace’s Cloud Servers technology, is to be added later this year. Cloud Files is a storage solution accessible via a RESTful API, while Cloud Servers is a technology offering Linux virtual images based on Xen Virtualization. NASA Nebula is a cloud computing service offering computing, networking and data storage services to NASA scientists, including the ability to process large scientific data sets.
OpenStack is for companies wanting to create their own cloud solution either for a their internal private use or to provide services to other users. Being an IaaS platform, OpenStack is going to compete more with Amazon and to a degree with Windows Azure, rather than Salesforce.com or Google.
Rackspace organized an OpenStack Design Summit on July 13-16, inviting technical advisors, developers and founding partners in order to present the code and establish a roadmap. A RightScale representative commented on the requirements gathering proceeding:
Despite the fact that there were over 40 technical folks discussing architectural details, Rick Clark [Chief Architect and Project Lead, OpenStack] managed the requirements gathering very openly using a “scaled-up” version of the Ubuntu design conference process he is very familiar with, having been the lead of the Ubuntu Server project. The process felt very inviting yet still focused on firming up a first release later this year, which doesn’t leave much room for crazy new stuff. I expect we’ll see a good number of companies contributing code to this project.
Over 25 companies, including Citrix, Dell, NTT Data, RightScale, AMD, and Intel, are supporting the project either by contributing with architectural ideas, code, or even using it as a business solution.
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Mobile and the New Two-Tiered Web Architecture
A practical guide to choosing the right agile tools
Getting Started with Stratos - an Open Source Cloud Platform
I wonder where this will take us?
Now how easy is it to do .NET programming under this model!
Maybe first release before year end.
Just wait. Microsoft will take care of you. You just need to wait.... :)
I'm not going to guess whether this is risky or not. The interesrting thing is that this area is hotting up. Testing ideas out in the real world will help to shake out a better future, I hope.
(In many ways the guys at the original PARC invented our current future in the 70's. Much of it was ideas that conventional wisdom said was plain stupid. (OO, Internet, GUI...) In fact Xerox senior management agreed that it wasn't their game so others capitalised on the output of the "thinktank"!)
Not sure what the MS comment means. MS has Azure and it's looking good. They seem to be going down a "closed box appliance" for third party deployment.
At the back of my mind I was wondering there about bringing some of the benefits of recent language developments (F#...) to whatever Rackspace is offering. If it's entirely under Linux that would mean Mono. There seems to be a disturbing trend to hunker down inside older language technologies, which sure means reduced productivity and reduced breadth of thought. I'd like to see an increase in the opposite trend!
Private cloud ... here I come!
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
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.
5 comments
Watch Thread Reply