#EJ PERFINO CODE#

#EJ PERFINO CODE#

And in fact, you indeed digged into the code and now are a committer of the Vaadin framework itself. But if you go with what the framework offers, you really don't have to do that. For example, when you want to 'break-out' of the framework and extend it yourself with new client-side functionality, you have to understand the orchestration that goes on behind the scenes. Of course there are drawbacks, but they are not especially significant for me. Mostly, my expectations have been met and I feel like the time for developing complex UIs is an order of magnitude shorter than it would be with some client-side frameworks. I'm fluent in Swing programming so learning Vaadin was extremely easy. Vaadin seemed like a silver bullet for me in how it combined backend and frontend development into a single layer, so I went with it. I compared a lot of frameworks, mostly client side based ones. Why did you decide to use Vaadin for Perfino? Persistence layers are great for applications with data from complex business domains, but not in our case. We need every extra bit of performance and we need total control over what is executed on the database. What about the persistence layer? What technologies do you use there? Via RMI, but that's only optionally the case if the collector needs to run in a DMZ. How do the frontend and backend communicate in Perfino? Our real backend is the collector which is not coupled to the UI, because it must be able to run in a separate process. In a sense, the UI code in Vaadin is both frontend and backend code at the same time, so yes, eliminating the transport layer between browser and server is priceless in terms of developer productivity. Would you say that development is simpler when your UI code is next to your backend code? One important external client-side component is yFiles for displaying call graphs, which I integrated as a Vaadin Javascript component. In the UI server we do not use any frameworks except for Vaadin. The collector is totally separated from the UI, and its most important external technology is a database. The most important part of Perfino is the agent which does not have any third-party dependencies apart from ASM. What kind of technologies are you “mixing” with Vaadin in Perfino? It's very easy to set up, has extremely low overhead and a really simple and transparent licensing scheme. We've used the experiences of our first customers to improve the tool and we're really confident that Perfino delivers excellent value. Perfino is a relatively new tool but it's now reached a mature state in version 3. There is a lot of data in the backend in our case and the easy incremental delivery of data to the browser makes it very performant for large tables. Indeed! Vaadin is a very good fit for the Perfino UI which falls into the 'admin UI' category. Congrats! I played with the demo and the UI components on it look familiar to me… what can you tell us about it? Me too! My Vaadin-based monitoring tool Perfino 3 has been released last week and I'm ready to talk about it and my general experience with Vaadin. Hello Ingo, it’s great to talk with you! I was really looking forward to it. Ingo is also a very active member of the Vaadin Community, having published a couple of add-ons, one of them recently merged into the core of Vaadin. Ingo and his team used Vaadin to develop the front end of their new product, Perfino, a promising JVM monitoring tool for production servers. Do the words JProfiler or Install4j sound familiar to you? Well, they are both popular products developed by ej-technologies and for this month’s Community Spotlight, I had the pleasure of talking with one of its founders, Ingo Kegel.

Ej perfino