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 Ryan Slobojan on Nov 11, 2008
The Apache Solr project, an open source enterprise search server based on Apache Lucene, recently released version 1.3. InfoQ spoke with Solr creator Yonik Seeley to learn more about this release, and also about what capabilities Solr offers to end users.
Seeley began by describing the target audience as "Pretty much anyone that needs a search box, faceted browsing (guided navigation) or a combination of the two", and identified the key features of Solr as:
Seeley also indicated that the major new features in this release are:
A comprehensive changelog is also available.
Seeley spoke in more detail about the scaling, capacity and relevance features of Solr, saying:
Solr is already deployed with collection sizes in the hundreds of millions of documents, and with the addition of distributed search, Solr should be able to handle billion document collections.
Solr has excellent full text relevancy, building on Lucene and easily providing term proximity boosting, recent document boosting, editorial boosting, and even custom scoring based on arbitrary functions of numeric field values.
AOL is using Solr to power it's channels: Music, NFL Sports, AOL Recipes, Reference Center, Real Estate and Autos being several examples. Solr also powers the search features of Netflix, Zappos, Gamespot, and the Internet Archive. There are *many* other big users I'm aware of that haven't publicly stated their use.
When asked about future plans for Solr, Seeley indicated that greater scalability, easier configuration and management of large cluster, location-based and realtime search and a refactoring to use Spring for configuration of plugins was on the horizon. Seeley also pointed out a mailing list post in which he discussed the future plans for Solr in more detail, in particular around the 2.0 timeframe.
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
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.
No comments
Watch Thread Reply