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 Apr 22, 2010
The Mono team has created a binding for Cocoa API, one of the major application environments for Mac OS, facilitating developers the possibility to write C# applications for Apple’s operating system.
Based on their success with MonoTouch, the Mono team has started the process of creating bindings for Mac’s main application framework, Cocoa. According to Miguel de Icaza, father of Mono, MonoMac has two types of bindings:
MonoMac is partially done, Mono is looking for contributor’s help to finish the rest:
- CoreFoundation (the parts that are needed, see the design principles)
- CoreText (done)
- CoreGraphics (done)
- Foundation (the parts that are needed, and helper tools to support the rest)
- AppKit (About 30% left to be done)
Mono had a similar project called CocoaSharp that was started back in 2004 by Geoff Norton with its first release in 2005. Plans were undergoing to progress with it in 2008, but de Icaza announced Novell was no longer interested to invest in its development in May 2009. de Icaza says they have used the lessons learned from that attempt to create a C# binding for Cocoa.
Monobjc is yet another .NET to C-Objective bridge. At version 2.0, Monobjc is a mature binding that facilitates programming against Mac OS X frameworks like Cocoa, WebKit, QuickTime and DiskRecording. The developer can access more than 1,400 classes and 7,000 methods on Mac OS X 10.4, 10.5 and 10.6. The bridge is integrated with MonoDevelop IDE and comes with documentation and Tutorials.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Federated Identity Management and Single Sign On
Getting Started with Stratos - an Open Source Cloud Platform
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