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 Robert Bazinet on Jul 25, 2008
Many developers who know a particular programming language and want to learn a second one, often find it the hardest language to learn but subsequent languages being easier. Any developer who knows C# and has an interest in learning IronRuby can find a tutorial series on learning IronRuby based on knowledge of C# from CodeThinked.
CodeThinked is a web site run by Justin Etheredge who has set out to show developers how to write Ruby from equal C#. The tutorial series currently has six parts but is ongoing and readers should continue to look for updates. The first two parts give the basics of getting IronRuby setup and then running some applications with it and the remaining four parts get into the heart of the tutorials.
Getting IronRuby Up and Running gives a good walk-through on how to get the source code from IronRuby.com using SubVersion and proceed to build IronRuby from source using Visual Studio 2008.
Getting IronRuby built and run successfully has some possible issues associated with it and Justin handles all of the scenarios he came up against, explains what they are and how to get around them.
Running Applications in IronRuby gets the developer started with writing Ruby and running under IronRuby. The tutorial starts off with everyone's favorite "HelloWorld" application and goes right into showing how to use the newly created class from other classes.
HelloWorld applications are always simple but give developers a way to see a running application with the littlest amount of work.
The tutorials start out with foundational information such as what it means to be a dynamic language. Justin jumps right into comparing various elements of C# that we use everyday such as the class keyword, building classes in C# and showing how they appear in Ruby. Various aspects of building classes such as getter and setters, different property types as well as class methods.
The tutorials progress into contrasting iterators such as C# foreach and for loops. There is always more than one way to solve a problem in Ruby and Justin helps point out what is considered the expected way in Ruby.
All four of the core parts of the tutorial are posted now:
Justin is taking a careful and detailed approach to showing developers parallels between C# and Ruby, his tutorials are well-worth reading. Later installments in this series on Justin's blog, CodeThinked.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
A Guide to Branching and Merging Patterns
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
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