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 May 26, 2010
Three months ago Microsoft released the Outlook PST Specification documentation allowing developers to create server/desktop applications processing PST content without having to install Outlook. On May 24th, Microsoft announced two new open source projects, PST Data Structure View Tool and PST File Format SDK, making the creation of such applications even easier.
Developers could access PST file content through the Messaging API (MAPI) via the Outlook Object Model since 2007. In February 2010, Microsoft released the complete Outlook PST File Format Structure specification in an attempt to help interoperability with other document processing systems. (The details were presented by InfoQ at that time.) The recently released PST Data Structure View Tool and PST File Format SDK offer a starting point for writing PST applications without having to deal with internal details of PST files.
The PST Data Structure View Tool is a MFC/C++ graphical tool developers can use to understand the internal organization of data in PST files. The PST File Format SDK is a cross-platform C++ library which offers read access to all items stored in a PST file. Microsoft promises to add writing capabilities in the near future.
Microsoft explains that opening up PST helps interoperability for clients with heterogeneous document systems and those having large amounts of archived PST data. Now, they can search through the PST data, extract and process it in various ways.
Both projects have been released under the Apache license.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Agile Maturity Model Applied to Building and Releasing Software
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