Max Gorin
Ranked 25 in Phase 2 with a weighted final score of 145

About the author

Interested in advanced Ruby techniques, real-life case studies, live coding shows - and meeting folks.

Multi-hundred-model apps with Rails and Netzke

What do you do when your Rails app needs to manage a hundred or two of data models? Like, you know, in the case of those "ERP systems" that help their users with accounting, call centres, logistics, backends, etc. If you're among those of us who have to deal with this - I feel your pain! Because for each model, you would probably write (or generate) controllers and views with overlapping functionality - like CRUD, search, export/import, etc. And soon you'd realise that this much code is far from being comfortably maintainable, so, you think: "I wish I had to write that code only once!" But how cooperative is Rails on this, really? Can you easily reuse your controller and view code? If you ever try, you'll know it's not a trivial task.

An extension to Rails called Netzke does not only provide you with a tool to create extremely reusable client-server GUI components capable of replacing Rails controllers and views, but it also gives you full-featured pre-built components (such as data grid) out of the box. You'll be amazed with how little code you can start creating solid web apps that handle all of your models. And if you need to extend, combine, or configure existing components - it's straight forward, because each Netzke component is, first of all, a Ruby class. Developing complex apps also becomes much easier due to the fact that Netzke components can be developed, tested, and shared individually, decoupled from the complexity of your application.

The client-side of Netzke apps is powered by Sencha Ext JS, which takes care of polished look and desktop-like experience familiar to any "business guy". Ext JS leverages modular approach to the client code already, which makes it a perfect match with the core Netzke concept of modularity.

This talk will give you the insight into the rationale behind Netzke - you'll learn how Netzke implements its "modular MVC", how it differs from Rails MVC, and what are the many advantages descending from that. You'll be presented with some cool Ruby code that will make you want to use Netzke in your next project. It will also become clear that Netzke is not a replacement for Rails, but a tool that makes your life a lot easier in the context of a very specific domain - the one of complex data-rich web apps.

Previous Next


  • Profile_image?user_id=383900952&size=bigger Ivan Ilves suggested 8 months ago

    Netzke allowed me to develop a couple of important apps in matter of days. I like almost every aspect of this framework. Looking forward to meet author. And yes, agree with Ebin J, Netzke will benefit from better documentation. :)

  • F85a6c654a0e18362381d4c51a5d8157?d=retro Paul Schyska suggested 8 months ago

    If that's whom I think (the author of Netzke), I have seen him back in 2010 on Rubyandrails Amsterdam and was very impressed with it. The guy is a great speaker and what he showed us just blew my mind. Looking forward to see him!

  • Bc90ae740f283e3239575965b3128de9?d=retro Ebin J suggested 8 months ago

    I am using netzke for all my rails projects. If some fine tuned documentation is given netzke will reach heights.

  • A35ec8515fd4d4755abe33722be41ff2?d=retro Dmytro Koval'ov suggested 8 months ago

    I've used Netzke to develop pretty complex application for banking sector, and really enjoyed cleanliness of the design. It allowed me to finish project in much shorter time than I anticipated.