coffeeaddict / kindergarten Goto Github PK

I can see that it's the default implementation for the guards, but I think this should be more generic. Perhaps a strategy adaptor for forwarding the method calls? This way you're not tied to a particular authorization solution, simply relying on one being provided.

Further to that, if no authorization is available, you can default to an always allow state.

I have a rails application in which I want to achieve the following:

a) Create a data access layer/service that hides the ORM models and exposes higher level methods (instead of ORM specific methods ... like say chained query building via where).

b) The reason why I need (a) is so that I can change the implementation of those higher level data access methods to instead use http calls or make RPC(via say thrift) calls later when we want to scale the system and split the app into front end and backend responsibilities, while keeping the code that consumes the data (relatively?) unchanged.

Can Kindergarten help me write that service/data wrapper ? How much would be the performance overhead ?

Since there is a dependency on activesupport ~> 3.2