Gulp on the other hand is written in the more usual NodeJS way with each function piping its output to the next, the data not being dumped to file until the end when you specify it to with a destination. Which you choose is really a matter of choice but the talk made it clear that if you’re not using either right now you should be. They will help simplify and automate your workflow. Now I just have to choose which one – they both look great to me.
The Jasper Reports talk was presented by Guust Nieuwenhuis. Jasper Reports is one of the most popular Java based reporting libraries and Guust highlighted that the report functionality in Adobe ColdFusion (up to but not including CF11) is actually a rather old version of Jasper Reports (version 1.7).
Jasper Reports is currently on version 5.6 and clearly if you are using one of these versions of Adobe ColdFusion or perhaps Railo, you could benefit a lot from using the more up to date versions. Guust ran through a demo of Jasper Reports, creating a report from his automated “love letter” application. He showed that it was a lot easier to get a pixel perfect report out of it than by using the version built into Adobe ColdFusion. What interested me most was that you can design the reports using an Eclipse plugin and get the reports to talk to the database server directly.
I could see this being useful for sites with quite a lot of data and on which reports can be quite intensive. One thing I would like to do is to run the Jasper reports against a replicated copy of live databases and therefore limit the resulting performance hit.
Fusion Reactor 5
“This is Fusion reactor, not ColdFusion, nor RailoFusion nor BlueFusion…” begins Charlie Arehart at the start of his talk on Fusion Reactor 5. His point being that Fusion Reactor works with any flavour of CFML engine and for that most Java-based application servers. At first glance Fusion Reactor appears to be a server monitoring tool with a nice dashboard. You can use it to keep tabs on the health of your server, how high your cpu usage is, memory allocated vs memory used etc. However, it is actually quite a bit more than that. It can be a powerful tool in tracking down problems seeing them before they bring your server down. It can report on the actual lines of code that error and also be used to identify and shut down long running requests. What impressed me was that all of this can be achieved with very limited impact on server performance. Its a credit to the abilities of the development team working on Fusion Reactor that they managed this. I would recommend implementing tools like this to clients who have business critical applications. Which, i think would admittedly be most clients. just for the increased visibility on potential problems.
Overall I found the CFCamp conference to be a very worthwhile experience. I left it with knowledge that would help me immediately in my day to day work. I also left with a number of things to continue looking into in the future. The main value I feel however comes from just being there. Being able to meet with other developers, discuss ideas, validate that we are heading in the right direction and confirming that we all come across the same difficulties. By networking like this we not only take away from it new knowledge but, we also help contribute to the CFML community.
On our return flight I have already had some ideas for talks at future conferences which I shall put forward to the organisers. Things that I think that would be quite interesting and useful to other developers. My first thought was to hold a problem solving workshop, getting the attendees to work together through a solution. The idea being to get people to see how others work and tackle problems. My next idea was an introduction to some of the gang of 4 design patterns but adapted to CFML.
I would definitely recommend going to conferences like this, CFCamp in particular. It was just the right size to have a variety of people with different skills and knowledge, but also small enough that interacting with each other was encourage and had an almost family vibe. Aside from some minor schedule changes with people unable to make the conference due to the train strike and the Lufthansa pilots strike it was a very good conference.
If you liked reading this article you may also like: