Skip to main content

My first experience with RoR

As I was thinking of implementing customized filterable datalists in Alfresco, my focus shifted to RoR. I had heard about RoR being simple scripting language that would help me in converting my thoughts to machine-actionable instructions! With the hope of creating the list in an hours time, I quickly committed myself to RoR inclusion.

RoR comes with its own set of problems. First the RoR examples that work with older version dont work anymore with 2.3.4. The latest version 3.0 was not available for download. Anyways, I downloaded, Aptana's RadRails 2.05 and started my experiments. RoR promotes convention over configuration. This looked very interesting and promising.

I had to struggle to get proper libmySQL.dll to get connected to my MySQL server. It seemed that Ruby 2.3.4 does not work with latest dll of MySQL (learnt from posts across the net). Finally, I was good to go. Indeed, I could get my first application (CRUD) in just 2 hours. Here are my initial opinions on RoR.

I consider RoR as another web framework, intends to ease the developer's effort. Its important to know Ruby programming constructs if you want to advance to next round of programming. Next, its important to unlearn old thinking and learn RoR related constructs, Form helpers, syntax, conventions. Thats too much for me who was looking to develop an app in a quick time. If I have to quickly get my application up, I better know RoR in detail. That simply states, I need more time to learn Ruby on Rails. Probably, developing an RoR application is easier, once I know RoR in depth! I have not lost hope.

I am now thinking of implementing the solution, with what I know already :) I will use YUI data table with JSON and use simple servlet in my Tomcat container. 'Known devil is better than unknown angel!!?'

Comments

Post a Comment

Thanks for your comments.

Popular posts from this blog

Key to adopt open source product

Friends, I am working on business solution implementation on open source product called Kaltura. Kaltura is a media management solution and has loads of features that compel any business to take a peek into it. More-over this is the only complete end-to-end open source software available to handle digital assets. But it comes with its own head ache. Considering its open source, its understandable. I feel, handling these would ensure you the success in your open source product implementation. 1. In my opinion, before adopting any open source software, build the capability to deal with the inconsistency bundled in the open source software. 2. I would avoid involving external consultants for 2 reasons.      a. I am not sure, they would bring necessary expertise on to table      b. I fear that there would be little ownership, they will not see big picture of my business (neither I am interested to share it all) 3. Alternative to that is to build the tea...
1 comment
Read more

GCP: Instance group

Managed instance group contains identical instnaces, created from an instance template. Supports auto scaling, auto healing, rolling updates, load balancing. VM instances are stateless and disks are deleted on VM recreation. It is possible for load balancer to send traffic to instance group through a named port. Configure autoscaling on and autoscaling policy. Auto scaling policy directs when to auto-scale, based on CPU utlization, HTTP load balancing utilization, Stack driver metric, or combination of the above. It is possible to specify maximum number of instances that can be in instance group. Enable auto healing through healhcheck configuration. Instance group while running, you can add/remove labels. You can do modifications just as you can do with an instance running. With instance group you can have rolling update, rolling restart/replace actions. When performing rolling update, perform canary deployment, and make sure that no rollback is needed. If rollback is needed, t...
Post a Comment
Read more

GCP: GAE - Memcache best practices

Memcache is a distributed in-memory data cache in front of or in place of robust persistent storage for some tasks. GAE includes a memory cache service for this purpose. Best practices for using memcache: 1. Handling memcache API failures gracefully; Do not expose errors to the end users 2. Use batching capability of the API when possible 3. Distribute load across your memcache keyspace Use sharding and aggregating for improving performance efficiency. Use TTL (expiration policy) to make sure the memcache does not fill-up indefinitely Use getIdentifiable() and putIfUntouched() for managing the values that may get affected by concurrent updates Use batching (getMulti ("comments", "commented_by") ) to fetch related values together instead of one by one Use graceful error handling
Post a Comment
Read more