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 Gilad Manor on May 28, 2010
The jQuery project started five years ago as the brain child of John Resig. jQuery was originally designed to handle cross-browser DOM traversal and manipulation. The current jQuery 1.4.2 version has evolved to include many additional tools intended to make JavaScript coding much easier. According to BuiltWith usage statistics, this open source JavaScript project is now used in over 30% of the top 10000 web sites.
The jQuery API is intended to be straightforward and intuitive. The API includes functionality for:
The jQuery framework uses a simple selector as the means of getting and manipulating DOM elements. Once an element in the DOM is obtained, it becomes a jQuery object and any library methods can be invoked on it. The jQuery framework allows the use of complex selectors as well, i.e. elements based on parent-child relationships, attributes and filters.
The Traversing (or navigating through the DOM elements) API include methods for advanced filtering of already-selected collections of elements, with methods such as filter(), is(), not() and slice().
Other traversing API are used for finding specific elements based on their relationships to other elements (as opposed to using id or class selectors) is also made easy with methods like children(), find(), contents(), next(), prev(), parents() and siblings().
Once a DOM element is selected (either by selection or creation), the jQuery manipulation functionality is available. This includes:
The CSS component provides a set of tools for getting and setting CSS properties of any element or collection of elements. Other tools in this category include the width() and height() methods as well as an offset() method for obtaining the relative offset of any specified element.
The jQuery framework provides a cross-browser implementation of working with events. Methods are exposed for defining and firing custom events, as well as bindings to standard DOM events. The jQuery framework also offers a wide range of event helpers, which wrap standard DOM events in jQuery functionality. This functionality is intended to make the reaction to things like clicks on particular elements possible with minimal code and no need for browser detection.
The jQuery Ajax API include methods for loading remote pages, data and scripts using get or post requests, simple access to JSON data and a set of custom AJAX events as way to work with the success, complete, start, stop and error events.
More documentation and tutorials on the jQuery framework also available, for getting started as well as more advanced plugins.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Monitor your Production Java App - includes JMX! Low Overhead - Free download
18 agile and lean practices for effective software development governance
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.
2 comments
Watch Thread Reply