We were planning to :
- modify the base source code of the Open Source Chef REST API
- use the internal source code of the Open Source Chef REST API in a Rack
But then, we have read that Opscode plan to do big changes in the code bases of
Chef Server (see below the references), for exemple, switching from Ruby to
So we are afraid that we will have to redo our work based on the actual chef
source code in some months.
Could you please give more information about the plan changes in code base ?
will the “chef-server-api\app\controllers” source code be totaly changed ?
if we write ruby code based on open source code of Chef, until when will it be
We are now thinking that we should only program based on REST API through HTTP
( initially we wanted to bypass the HTTP and authentication layer).
Thanks in advance for your feedback.
In short, Chef is converging the code bases of their three products (hosted,
private and open). The primary change on this will moving from CouchBD to a SQL
based DB and moving away the API calls away from Merb/Ruby to Erlang. They are
also improving search so that we can make more fine-tuned requests that perform
better and return less extraneous data.
Rob Hirschfeld’s Notes
Chef <3 Erlang
moving to more Erlang on REST APIs, made a 2x in memory use difference
Erlang bits have realy steady performance
Erlang Chef Server - Chris Brown
Write docs on operating the erlang server
On the server side, we can expect a lot of performance improvements as
chef-server moves from ruby + couchdb to erlang + mysql. This may happen sooner
than one might normally expect as Opscode has already converted part of Hosted
Chef to Erlang and MySQL, it just hasn’t open-sourced that code yet.