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 Dilip Krishnan on Oct 16, 2009
Bridging the gap between business and IT has always been, for the most part, a pipe dream for many a sponsor of SOA initiatives. According to the Business Ecology Initiative (BEI); whose purpose is to refocus such initiatives from a technology and data oriented perspective to one that is optimized for business benefits, processes, and roles; nurturing business driven IT, is the only way bridge this gap and create a business ecosystem.
The SOA Consortium, for which BEI is an umbrella organization, recently rebranded itself as the SOA/BPM Consortium, its clearly becoming apparent as to why SOA may be dead as we know it. There has been a lot written about BPM and SOA. It is clear that the two have their synergies, Not having the clearly defined best practices, roles, processes however, is one of the challenges BEI is trying and address. Bridging the gap between BPM and SOA for successful business driven IT,
SOA takes a technology-based approach to creating an architecture that supports the capturing of business processes and extending these for new capabilities while BPM takes a process management approach that may or may not include technology. Business and IT need to forge a closer relationship, so the new advocacy group will be focused on helping organizations combine the technically oriented aspects of SOA with the business focus of Business Process Management (BPM). Together they can create an environment that brings together the technology requirements (an architecture to support a service oriented approach to process) and the business management of these processes to support Business Ecology.
In a press release, Richard Mark Soley, executive director, SOA Consortium, recounts the history of the consortium and its mission and how the newly rebranded SOA consortium will act as a working group to impact the “business ecology”.
When the SOA Consortium began, SOA was more of a fringe methodology that only a few organizations were doing with any great success, rather than an accepted part of an overall business strategy. Three years later, we see corporations large and small using the principles of SOA to enhance their overall business and technology strategies, As we move forward in the drive towards Business Ecology, the combined BPM/SOA Consortium will continue to engage with the business community to show how SOA can be a valuable part of their business optimization efforts.
According an EbizQ article, the BPM/SOA Consortium includes Fortune 200 companies in Financial Services, Travel, Manufacturing, Retail and Telecommunications. Sponsors include Appian, IBM Corporation, MegaPractical and SPARX Systems, Inc. Participants include Fortune 1000 corporations, major government agencies and non-governmental organizations. For more information, please visit www.omg.org/consortiums.
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.
No comments
Watch Thread Reply