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 Jonathan Allen on Mar 11, 2008
Even before tools like Reflector made it easy, decompiling .NET applications has become standard operating procedure. Common reasons to decompile an application include learning how compiler's translate code, working around a library's limitations, or outright stealing another person's work. In the world of web browsers, it is so common that "view source" is a primary means of learning how to program.
Setting aside the legal implications, decompiling a Silverlight 2 application is a simple matter. All of the files needed for a Silverlight application are stored in a single ZIP file called a XAP. It contains all of the XAML, DLL, and config files needed by the application. Once extracted, the DLLs can be opened with ILDASM or your favorite decompiler.
If you are interested in learning more about XAP files, check out Pete Brown's blog.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
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