i have running project comprised of set of microservices. planning introduce vagrant new developer joins team able set environment , running on his/her machine.
i have been reading through vagrant while , looks interesting. i'm starting out simple. initialized 1 of microservices using vagrant created vagrantfile. approach? 1 vagrantfile per microservice?
i attempted create box microservice. name should box have? should stick naming conventions? how , should box persisted? should part of source code of microservice component?
i see you've asked similar , possibly duplicate question stuff well.
i'm not sure why you're capitalizing microservice, i'm not aware of software named that.
vagrant, , virtualization/vms in general, let choose system architecture - people try choose close production or be. if have small site , run off shared box or vps, having installed in 1 vagrant box , provisioned such (either docker or simple shell provisioning scripts) fine.
if have multiple servers in production (www, app, db, whatever), have choice. can still provision of roles 1 vagrant box, or can launch multiple boxes each trying replicate roles (see multi-machine vagrant) - situation might prefer docker on shell provisioning scripts. presumably use same or similar docker configuration across environments (dev, qa, production, etc).
the questions in last paragraph,
what name should box have? should stick naming conventions? how , should box persisted? should part of source code of microservice component?
are , development , deployment workflow. in multiple developer environment, store vagrantfile along source code in version control, developers can work same development environment, , quick , easy onboard new developers or nuke box , start again if working on deployment , provisioning.
- naming box, , naming conventions not required , you
- persistence of box not high priority - idea can , (every few hours, days, once week, etc) recreate box
- i can't if should store
vagrantfilesource code, depend on team composition, development workflow, etc
Comments
Post a Comment