Hey Curtis,
Thanks for reaching out. Glad you find Concourse compelling :)
1. I wouldn't recommend using Concourse in production today, but I think we'll be ready for production in about 6 months. Everything is ready from a correctness standpoint, but I want to improve performance a bit before we start recommending production usage.
2. Yes, development is still very active! 0.5.0 has been on the roadmap for a while and it'll be ready for release by the end of this month (October). We've been concurrently developing 0.5 and 0.6 (which will bring distributed cluster support) which is why the development has gone on longer than expected. The nice part is that 0.6 will be released a couple of months after 0.5 instead of much longer after.
3. It's not designed for embedded use, but it
can be done. If you're okay with Concourse running in a separate process, but that process being completely managed by your host application, then you can do something similar to what we do in
testing framework. If you want it to be truly embedded such that Concourse runs in the same process as your host application, then it can be done if you include the concourse-server jar (and all its dependencies) in your project.
You'd be able to create an instance of the server like:
ConcourseServer server = ConcourseServer.create(port, bufferStore, dbStore);
Runtime.getRuntime().addShutdownHook(new Thread(new Runnable(){
@Override
public void run() {
new ShutdownRunner().main();
}
}));
And then you could create a client connection to the embedded server like:
Concourse concourse = Concourse.connect("localhost", port, "admin", "admin");
4. Yes, documentation will be greatly improved over the next couple of weeks. We're working on a new website that'll feature more in depth guides with code samples, etc. That's one of the big pushes that'll be released alongside version 0.5.