{"action":"created","issue":{"url":"https://api.github.com/repos/thbar/kiba/issues/20","labels_url":"https://api.github.com/repos/thbar/kiba/issues/20/labels{/name}","comments_url":"https://api.github.com/repos/thbar/kiba/issues/20/comments","events_url":"https://api.github.com/repos/thbar/kiba/issues/20/events","html_url":"https://github.com/thbar/kiba/issues/20","id":95219962,"number":20,"title":"Define the Kiba Pro offering","user":{"login":"thbar","id":10141,"avatar_url":"https://avatars.githubusercontent.com/u/10141?v=3","gravatar_id":"","url":"https://api.github.com/users/thbar","html_url":"https://github.com/thbar","followers_url":"https://api.github.com/users/thbar/followers","following_url":"https://api.github.com/users/thbar/following{/other_user}","gists_url":"https://api.github.com/users/thbar/gists{/gist_id}","starred_url":"https://api.github.com/users/thbar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thbar/subscriptions","organizations_url":"https://api.github.com/users/thbar/orgs","repos_url":"https://api.github.com/users/thbar/repos","events_url":"https://api.github.com/users/thbar/events{/privacy}","received_events_url":"https://api.github.com/users/thbar/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/thbar/kiba/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/thbar/kiba/labels/kiba-pro","name":"kiba-pro","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-07-15T15:13:33Z","updated_at":"2015-12-03T14:30:54Z","closed_at":null,"body":"As first mentioned [on my blog](http://thibautbarrere.com/2015/06/04/what-s-ahead-for-kiba-etl/#kiba-pro-on-steroids-yearly-subscription) I plan to launch a Kiba Pro offering. Please comment here or [email me](mailto:thibaut.barrere@gmail.com) to discuss more details, manifest your interest and support, this will be greatly appreciated.\r\n\r\n## Sustainable OSS\r\n\r\nEspecially after maintaining activewarehouse-etl for quite a bit of time, I'm willing to find a sustainable way to keep a high quality ETL solution for Ruby for the years to come, without killing my solopreneur-business.\r\n\r\nIf I'd paraphrase Mike Perham's statement with Sidekiq-Pro (see [Sidekiq-Pro FAQ](https://github.com/mperham/sidekiq/wiki/Pro-FAQ)), \"Kiba Pro is (well, will be) an extension which adds a few nice features to Kiba. Kiba is open source and free for all to use but unfortunately it takes a lot of my time to maintain and support. Kiba Pro is a way for you to purchase really useful functionality while also ensuring Kiba will be supported for years to come\".\r\n\r\nA recurring yearly subscription similar to [Sidekiq Pro](http://sidekiq.org/pro) would secure some of my time to maintain and improve the solution and avoid the fate of activewarehouse-etl.\r\n\r\n## Potential features\r\n\r\nFeatures could include:\r\n\r\n* multi-threading (and later, multi-machines) - commonly requested\r\n* built-in sources/transforms/destinations for common tasks\r\n  * lookups\r\n  * upserts / bulk load modules\r\n  * connectors optimized for parallelism (HTTP pagination extraction)\r\n  * connectors for the cloud (RedShift, ...)\r\n* built-in helpers for common operations (debugging, limiting, caching...)\r\n* premium support\r\n\r\n## Interested? Please chime in!\r\n\r\nI'm pushing this publicly for transparency and also to find the \"good\" feature set, the one that larger companies would be willing to support my work on Kiba while getting extra value.\r\n\r\nDo not hesitate to [email](mailto:thibaut.barrere@gmail.com) me if your company could be interested in supporting richer features."},"comment":{"url":"https://api.github.com/repos/thbar/kiba/issues/comments/161656198","html_url":"https://github.com/thbar/kiba/issues/20#issuecomment-161656198","issue_url":"https://api.github.com/repos/thbar/kiba/issues/20","id":161656198,"user":{"login":"mroby-dresources","id":12515685,"avatar_url":"https://avatars.githubusercontent.com/u/12515685?v=3","gravatar_id":"","url":"https://api.github.com/users/mroby-dresources","html_url":"https://github.com/mroby-dresources","followers_url":"https://api.github.com/users/mroby-dresources/followers","following_url":"https://api.github.com/users/mroby-dresources/following{/other_user}","gists_url":"https://api.github.com/users/mroby-dresources/gists{/gist_id}","starred_url":"https://api.github.com/users/mroby-dresources/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mroby-dresources/subscriptions","organizations_url":"https://api.github.com/users/mroby-dresources/orgs","repos_url":"https://api.github.com/users/mroby-dresources/repos","events_url":"https://api.github.com/users/mroby-dresources/events{/privacy}","received_events_url":"https://api.github.com/users/mroby-dresources/received_events","type":"User","site_admin":false},"created_at":"2015-12-03T14:30:54Z","updated_at":"2015-12-03T14:30:54Z","body":"Any chance of automated rollback or versioning? You can roll your own, but it would be great to have a common way of handling it as part of the ETL process for frequently updated data."}}