ProjectX has officially been named Baratine.

Baratine is an Object Oriented approach to building reactive systems in the JVM. As our previous blog posts have alluded to, Baratine presents a simplified programming model, where thread & data are merged. This allows programmers to build REST-like, MVC-like, Websocket, or any other modern web application without having to deal with:

• Cache Coherency Issues
• Synchronization Code Blocks
• Database Bottlenecks

Rather than being another Yet Another Framework to Learn, Baratine leverages a model that is familiar to Spring, Java EE, and Servlet programmers. Baratine allows programmers to write single component MicroServices that are automatically scalable & shardable. Whereas a typical enterprise application may use technologies such as:

• Spring Framework - For Inversion of Control
• Servlet Engine - For Business Logic Processing
• Hibernate - For Object relational mapping and persistence
• Apache Axis - For Web Services
• JasperReports - For Page rendering & display
• Distributed Cache - For Performance & speed

Baratine manages to replace all of these as a single 8 MB component! Because Baratine has a unified thread and data model, it not only replaces them but it also provides:

• Nonblocking Performance - Millions of operations per second per instance
• Synchronization Free Code - Modifying data does not require synchronization
• No integration Points - Single component, create a microservice, deploy it anywhere
• Polyglot integration - Write clients in any language: Ruby, Perl, Python, Javascript, etc
• Less lines of code - No ORM mapping, no XML config, no dependencies, just POJOs
• And More!

Read exactly what technologies are supporter by Baratine at the Baratine blog!

Read how we created a Distributed Search Server out of Apache Lucene, that outperforms Apache Solr!

For entire code examples, refer to our GitHub Page

Resin Cloud Support Overview

Cloud support is Resin’s 3rd generation clustering. It is based on years of perfecting ways to setup and manage a cluster. It is the culmination of decisions about the best way to do things. Caucho has been doing clustering with Resin longer than many other companies existed, and longer than many of the big players were in the Java market. Our clustering predates most if not all other solutions. And our clustering support is not bolted on as an after thought. We didn’t buy it. Caucho is an engineering company. We built it. We perfected it. It is not just built in, its ingrained in. Resin is designed from the ground up to support clustering and cloud computing. (more…)

The Caucho team just got back from Las Vegas for TSSJS and we had a great time. TSSJS is a really good conference to attend, especially from the point of view of a company like Caucho, because there is a real developer focus. The people there build real server-side applications and know what they’re doing. There were a number of questions about Resin, our own Reza Rahman gave several talks (including a keynote on Resin), and I got to see some interesting presentations from a wide variety of speakers.

(more…)

We at Caucho are very excited in working steadily towards getting Resin certified on the recently finalized Java EE 6 Web Profile. Along with GlassFish and JBoss, we are aiming to provide one of the earliest solid implementations for Java EE 6. In fact, Resin is the only major application server focused solely on delivering a very lightweight implementation targeting just the Web Profile.

This blog entry briefly discusses the Java EE 6 Web Profile, what it offers and how it fits with the lightweight development philosophy of Resin as well as the details of our implementation including Resin extensions to the Java EE 6 Web Profile.

(more…)

For version 4.0.1, we have added Quercus compilation support for other application servers including Tomcat, where before the interpreted mode was only available. The compiled mode is significantly faster than the interpreted mode (though the interpreted is still quite speedy compared to PHP on Apache). Quercus compilation will also work on Google App Engine, but there’s a requisite that files be pre-compiled.

(more…)

If you’re on Facebook, check out our Caucho Technology page. It’s updated regularly with the latest news and announcements.

2008 has been a great year for Caucho and we’d once again like to thank our customers, users, and community members for their support! This year we’ve seen

• Resin 3.1 become stable
• The introduction of BAM and Resin 3.2
• New large-scale deployments of Quercus
• A new streamlined Hessian
• Early snapshots of Resin 4.0 featuring cloud computing and OSGi

But we’ve made more than just technological strides over the past year — we’ve also been reaching out to the community:

• As Caucho’s evangelist, I had the chance to speak 8 times this year
• I’ve written 4 articles about Caucho products
• We created a Caucho Newsletter
• We launched a new training program
• We started this blog

Thanks again for a great 2008! See you in 2009…

During my talk yesterday at Devoxx, my laptop died about halfway through. Fortunately for me, Toni Epple stepped in and loaned me his laptop to finish up the presentation and even had a demo ready for me! Toni and I met the day before at the speakers’ dinner where we talked about Quercus and the new NetBeans PHP support. I hadn’t had a chance to look at it yet, so at the dinner I couldn’t say whether they worked together or not. The day of the talk, Toni stopped by the Caucho booth to try to get Netbeans to deploy WordPress to Quercus and we got it working quite easily on his laptop. He let me use that same laptop and the deployed WordPress as a demo when my machine died. What luck!

This just in… in the middle of writing this blog entry, one of the audience members from yesterday came to talk to me at the booth and told me that the same thing happened to another presenter at a BOF later in the day! I was using my laptop with Windows, then I tried another Windows machine which didn’t work, and finally Toni’s Mac saved me. In the BOF, there were again two Windows laptops that failed then a Mac saved the day again. I’m pretty sure what my replacement machine should be now…

Watch this blog for my presentation and either a description or a screencast next week of the demo I was planning to do. It’s actually a nice little example of how to profile and optimize a PHP app with a Java profiler. It will use our built-in Resin profiler that I modified last week to have a special Quercus mode.

Thanks once again to Toni for his help and check out his blog post about getting the NetBeans PHP and Quercus to work together. Thanks also to all the other attendees for coming and for their patience!

I haven’t had much chance to get away from the booth much here at Devoxx, but I managed to sneak away to blog a bit about what’s going on. For the most part, I’ve just been meeting a lot of smart people who stopped by our booth (just look right when you enter the convention floor), but I also got to see Peter Kriens’ talk yesterday on OSGi. (Summary: services are the true innovation of OSGi - bundles just support their encapsulation.) Last night’s speaker dinner was nice as well. I got to talk to a lot of JUG leaders from around the world and many of the speakers. A lot of the same faces make the rounds at these conventions, but the good news is that many of them are highly qualified, intellegent, and experienced speakers. I got a chance to talk to a few guys from the Glassfish team about the direction of the JavaEE standards and Jersey. Top-notch engineers.

If you get a chance, please come to my talk later today at 16:40-17:40 in theater 7. That’s right, Theater 7. The venue here is great because we have a full movie screen on which to project our presentations. Time to check my resolution…

In case you haven’t noticed or checked out what we’ve been doing with BAM, now might be a good time. BAM takes its inspiration from XMPP, but expands it into a fully-fledged enterprise message architecture. What this means for developers is that we’re presenting a much cleaner, easier, and more composable framework in which to write your message-based apps compared to SOA and JMS-style approaches. How do we know it’s cleaner and easier? We’re using it ourselves as the basis for our next-generation of Resin for advanced clustering features, remote deployment, and even JMS. This being said, BAM is still in development so it might take a couple of releases before we declare it stable.

If you’re interested in checking out BAM, come on out to the Silicon Valley Code Camp this Saturday to see me talk about it.