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 Jean-Jacques Dubray on Sep 07, 2010
Rod Johnson published last week a quick introduction to VMware Cloud Application Platform, VMware vFabric, as part of the latest iteration of their Cloud Computing Vision:
This platform delivers on the promise of VMware’s acquisition of SpringSource, pulling together our assets into a single, next-generation infrastructure. While the respective components will remain available separately, we believe this integrated offering will provide a simpler, more efficient, option. [It] combines the Spring development framework and tools with VMware vFabric platform services that enable fast delivery of next-generation applications that are instantly scalable and cloud-portable.
vFabric is a unified platform that offers instant scalability and is cloud-portable. It builds on Spring assets:
[The] Spring Framework including security, batch, integration, tc Server and Hyperic; SpringSource Tool Suite, Grails and Spring Roo; Rabbit Technologies and GemStone Systems;
From Rod's point of view, IT needs a platform that is free of the complexity, bloat and limitations of prior-generation architectures:
The rise of virtualization and cloud computing combined with the popularity of consumer and software-as-a-service applications [...] are driving significant shifts in application architectures – across infrastructure, applications, data access, and how end users interact with applications. Modern applications need to be easy to use, data rich, and provide access anywhere, anytime. Developers need the frameworks, tools and platform services that enable them to build great applications and immediately deploy those applications onto an intelligent platform that provisions itself on demand and scales the application based on policy.
He explains:
The shift toward cloud computing tends to mix developer and operational concerns [...] The path to cloud begins with developer tools and features that make it easy to create [Cloud-based] applications.
VMware vFabric [is based on] tc Server and Hyperic [... and supports] new approaches to data management that enable applications to scale across elastic, geographically distributed cloud architectures with our GemFire and RabbitMQ technologies.
One of Rod's reader, "Fetch", asked:
What does this mean for CloudFoundry? The two offerings seem to be reasonably similar in that they both involve "simple deployment to the cloud" for developers using SpringSource toolsets, however the deployment is to different hosts/infrastructure.
Rod responded:
vFabric is targeted at enterprises that want to modernize their own datacenter or IT infrastructure and gain private cloud capabilities. Services like CloudFoundry and our partnerships with Salesforce (with VMforce) and Google (with Google App Engine) are for customers that want to leverage someone else’s datacenter, i.e. public cloud. Of course, building your applications with Spring will help you with portability and give you choice about whether to deploy your application in the public cloud or your own private cloud.
Today all but the major actors of the Cloud are moving towards PaaS. Is it the right direction for Cloud Computing? Is IaaS "dead"? What are the ideal characteristics of a PaaS? Have you experimented with PaaS? What benefits and drawbacks do you see for your IT organization? Are we going to need multiple PaaS? or does one PaaS fits all?
VMware's Utility Cloud Computing System Architecture now published here. Reading this clearly sheds light on VMware's cloud developments.
www.scribd.com/VMware-Cloud-Utility-Computing-S...
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.
1 comment
Watch Thread Reply