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 Dec 29, 2009
Markdown Sharp, initially called Markdown.NET, a C# implementation of the Markdown text processor, has been open sourced by Stack Overflow.
Markdown is a text-to-HTML conversion tool initially written in Perl by John Gruber who released it back in 2004 under a BSD license. Markdown is one of several lightweight markup languages - AsciiDoc, BBCode, Textile, etc.- and has got some traction over the years being employed by websites like Stack Overflow.
There are several Markdown implementation besides the original one done in Perl: PHP Markdown, Markdown.NET, Showdown/JavaScript, Discount/C, RDiscount/Ruby. Stack Overflow has been using WMD, a JavaScript implementation of Markdown, on the client side and Markdown.NET on the server side. WMD was open source from the beginning, and it was the effort of reverse engineering the original WDM/JavaScript written by John Fraser of AttackLabs. The server-side C# implementation has been recently open sourced as Markdown Sharp with some improvements, bug fixes and additions:
- included relevant links, documentation, and related files
- added MDTest 1.1 test suite
- added Simple test suite
- both NUnit and console runnable tests
- standard Benchmark with short, medium, and long Markdown samples
- refactored and profiled for 2x – 5x more performance
- the Stack Overflow specific changes (such as stricter italics/bold) are configurable, so you can toggle them on and off.
Markdown is useful to writers who want to use a simpler-than-HTML markup language that later can be converted to HTML. Also, websites can use it to let users enter comments in plain text which then are converted to HTML for publishing.
Mobile and the New Two-Tiered Web Architecture
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
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