Tracking change and innovation in the enterprise software development community
Content in this box provided by our Sponsor:
What Is Terracotta?
Terracotta is Network-Attached Memory and is open source infrastructure software that makes it easy to scale a Java application to as many computers as needed, without the usual custom application code and databases used to share data in a cluster.
Terracotta manages mission critical data using Network-Attached Memory (NAM) technology. NAM enables Terracotta to cluster Java Virtual Machines (JVMs) directly underneath applications, and is a proven runtime approach to providing Java applications both high availability and scalability.
What's New in Terracotta 2.7?
Terracotta 2.7 is a key follow-on release to Terracotta 2.6., featuring platform support for Spring 2.0.8, Spring 2.5.3 and Glassfish V2. Other key features include:
Where Can I Get Terracotta?
Terracotta is Open Source software which you may freely download and use by clicking here.
Where Can I Get Terracotta Training and Support?
Terracotta offers a range of Enterprise Offerings designed to help you to get the most out of Terracotta. Offerings include the Enterprise Subscription, Developer Support, Consulting Services and Training.
Terracotta Whitepapers
Terracotta ROI
Terracotta Blogs
Terracotta Forum Discussions
Terracotta Community Links
Terracotta Introductory Videos
In this interview taken by InfoQ’s Ryan Slobojan, Dan Farino, Chief Systems Architect at MySpace, talks about the system architecture and the challenges faced when building a very large online community. Because MySpace is built almost entirely on the .NET Framework, Dan explains how a .NET product scales on hundreds of servers.
The ways to cache a web application are numerous and often complex. Apart from the very basic page caching, Rails 2.2 introduced conditional GET through the use of HTTP headers: last_modified and etag. Following most of the internet standard caching section of RFC2616, Ryan Tomayko released Rack::Cache.
Ruby's implementation of Net::HTTP has serious performance problems in the current version 1.8.6, caused by some implementation details. Luckily, both Ruby 1.8.7 and 1.9's implementation performs much better.
In this article, Steven Haines talks about web application performance tuning which used to be more of an art than science. He proposes a method called wait-based tuning, making the entire process more measurable and, consequently, more scientific.
Rails 2.2 is schedule to be thread safe - but will blocking I/O libraries make it necessary to run multiple Ruby instances? We take a look at how non-blocking I/O and Ruby 1.9's Fibers help solve the problem. We talked to Mohammad A. Ali of the NeverBlock project and Tony Arcieri of the Revactor project.
In this interview filmed at RubyFringe 2008, Tom Preston-Werner talks about how both Powerset and GitHub use Ruby and Erlang, as well as tools like Fuzed, god, and more.
In this interview, Avi Bryant talks about the Smalltalk web framework Seaside, DabbleDB, using Smalltalk images for persistence instead of an RDBMs, GemStone and more.
In this presentation from RubyFringe, Tobias Lütke talks about memcached, the widely used caching solution. Tobias explains how to use it and gives some practical tips on what not to do.
In this presentation, Dan Pritchett addresses latency issues in web applications that should be dealt with from the beginning when the system is designed. Dan offers some practical solutions to latency.
