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 Boris Lublinsky on Sep 11, 2008
In a new article, SOA architect Alex Maclinovsky discusses an approach for building an extensible SOA infrastructure directly supporting SOA governance. According to Alex,
A combination of processes, practices and tools which facilitate lifecycle of Enterprise Services and provide means for creating, communicating, enforcing and managing compliance to corporate policies regarding the non-functional service characteristics that are of importance to business today.
The ideal SOA infrastructure has to be extensible by design so that support for new policies, required by organization, can be easily added. The result of this design was Aspect-Based SOA infrastructure, allowing to add additional software services to the existing platform. According to Alex:
... a fundamental reason why we could not enumerate all the characteristics of SOA services that would make them suitable as the computing platform for the Enterprise. That reason was that these characteristics were based on the actual business, regulatory and other requirements which were bound to vary by industry, geography, from client to client, and, most importantly, with time.
Such infrastructure, directly supporting SOA Governance is what
turns Enterprise Services from digital artifacts into true business assets by allowing responsible reuse across the domains of control of SOA participants.
Check out Alex Maclinovsky ‘sarticle, Quest for True SOA for more information.
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