Docker compose for Feast

[woop]

We've had requests for a Docker Compose script to initialize a Feast deployment. This would make it easier for Non-Kube based deployment, especially during quickstarts or tests.

The proposed use case here is for a single docker-compose up to bring up a running Feast deployment. It should minimally include

• Redis
• Kafka
• Feast Core
• Feast Core DB
• Feast Serving

The default configuration can be used for these components. The existing Helm installation can be used for reference.

[khorshuheng]

As discussed, i will start working on this.

[ches]

We have this done, although it is probably more than what many people developing on the project would want all the time because it includes containers for dev with Cassandra and Hive as well. We could structure a base docker-compose.yml with the components given above, and an extra one or two for extending the base if developing/testing for those storage options.

[woop]

We have this done, although it is probably more than what many people developing on the project would want all the time because it includes containers for dev with Cassandra and Hive as well. We could structure a base docker-compose.yml with the components given above, and an extra one or two for extending the base if developing/testing for those storage options.

Wow that is great news!

I think your approach makes sense. The primary group I would like to target with Docker Compose are end users who aren't familiar with Minikube or Kubernetes. Would be great if we could get them up and running and testing the system. Developers would also benefit from the availability of this.

I don't really have strong feelings on which stores to start with, but having an opinionated default with some options would make sense.

[woop]

This is resolved in #328