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 Aug 13, 2008
Microsoft has recently released Sync Framework 1.0 RTM. According to Microsoft, Sync Framework is "a comprehensive synchronization platform that enables collaboration and offline scenarios for applications, services and devices".
Sync Framework is useful for:
Developers can build sync ecosystems that integrate any application, any type of data, using any protocol over any network.
Rob Tiffany, Senior Technical Product Manager for Windows Mobile at Microsoft, describes the Sync Framework:
Imagine being able to build a solution that seamlessly exchanges contact information between Outlook, a database contact management application, your mobile device and your service based contact management system. Or how about a mobile device that connects with other devices to exchange pictures and videos. How about being able to take data from any of your enterprise databases, file or enterprise systems and make it available offline for users to modify and sync back up to the enterprise.
Some of the key features of Sync Framework are:
Sync Framework contains Sync Services for ADO.NET which is a "solution for synchronizing ADO.NET enabled databases in offline and collaboration scenarios".
Sync Framework also contains Sync Services for File Systems which is "one of the providers included out-of-the-box that enables synchronization of files between devices".
Sync Framework is offered free for Windows, and can be licensed in order to be ported to other platforms.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Transforming Software Delivery: An IBM Rational Case Study
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
There are potential issues around conflict identification and resolution in the architecture upon which the sync framework is based.
I've outlined some of these in my blog:
Occasionally Connected Systems Architecture
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