In this part of a series of tutorials, we’re building a microservice architecture with CockroachDB writing changes in real-time to an S3 bucket in JSON format.
Join the DZone community and get the full member experience. This is my second post on creating a multi-service architecture with docker-compose. We’re building a microservice architecture with CockroachDB writing changes in real-time to an S3 bucket in JSON format. S3 bucket is served by a service called Minio. It can act like an S3 appliance on-premise or serve as a local gateway to your cloud storage. You can find the first post here. To get started with Minio container, the easiest step is to just look at their quick-start guide This pulls the latest stable Minio container, maps a host port 9000 to the Minio container and starts the container mapped to a volume called /data. One neat trick I just learned is to name your service with container_name, that way we can reference the containers by name and not search docker ps for container ID. So let’s add the property to crdb and minio respectively. The whole file should look like so: You can now access the container by name, instead of ID! Minio: CockroachDB: Invoking bash varies based on the base image container is using, hence the difference between bin/sh and bash respectively.
