2 ms·
This looks somewhat similar to what we're doing at my current job. We've writing APIs for our internal systems to decouple things a bit, and have ended up with
by chriswarbo 12y ago
This looks somewhat similar to what we're doing at my current job. We've writing APIs for our internal systems to decouple things a bit, and have ended up with a frontend router, a "middle-end" message queue and backend scripts to do the processing.
However, our Vagrant setup just took a massive turn for the worse: due to some compatability issues, these VMs have now all been hooked together using Puppet! During provisioning, if the git repos for the other machines aren't checked out to a particular location, everything dies; which seems like a really cargo-culty choice to me.
I'd be interested in doing things like this with Nix: Disnix to define the relationships between the servers and NixOps to define the VM provisioning. That may be because I'm a functional programming nut who's just switched to NixOS though ;)
- vegancap 12y agoI've only been using this structure for say, an app and an API. I haven't tried it with say caching vm's or a message server thrown in the mix. Your idea about using Nix might be worth me looking into next! It kinda feels like spinning plates trying to organise vm's and codebases haha. I thought this structure might be a good start for new comers though :)