This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-14
Channels
- # aatree (1)
- # admin-announcements (1)
- # beginners (12)
- # boot (359)
- # cljs-dev (23)
- # cljsjs (2)
- # cljsrn (1)
- # clojure (53)
- # clojure-czech (5)
- # clojure-madison (1)
- # clojure-russia (15)
- # clojured (8)
- # clojurescript (16)
- # community-development (2)
- # core-async (6)
- # cursive (19)
- # datomic (31)
- # emacs (48)
- # euroclojure (3)
- # hoplon (29)
- # microservices (7)
- # mount (46)
- # off-topic (7)
- # om (11)
- # proton (74)
- # reagent (4)
- # spacemacs (3)
Hi everybody, how are you dealing with microservices in a dev environment? For production environment there are lots of solutions approaches like deploying each microservice in a docker container and use some kind of docker orchestration i.e. Kubernetes, Swarm, etc but when it comes to development environment it is a unknown, nobody publishes any article about it - including the big players like netflix, spotify, etc
I'm using a not-so-good approach. For each project (set of microservices), I create a meta git repository which contains a docker-compose file and some configuration (database seed, readme.md with instructions of how to run the whole project, etc), usually it contains scripts to create database schemas for each microservice, avoid spawn a new database instance for each one
it works quite well when you have a limited amount of microservices, usually less than 10
apart from that, docker consumes a lot of IO to run containers, so spawn more than 10 containers with a regular HD is not so pleasant