Open zackdouglas opened 10 years ago
Resurrecting the zombies...
How did you want to use Docker? A monolithic container? I'm not really sure how you guys want to split up the project.
I'm thinking 1 container for the frontend, 1 container for the api, 1 container for the DB. Frontend would just talk via REST or WS to the API, and the API would talk to the DB via ambassador link.
To me docker is optional. We can split it up into separate containers, but not sure if it's really necessary since it's original purpose would just be handling a limited number of connections.
Regards, Jarrod B. Reuter
Cell: 614-805-4018 Web: http://jarrodreuter.com/
On Tue, Jun 14, 2016 at 7:54 PM, iparanza notifications@github.com wrote:
Resurrecting the zombies...
How did you want to use Docker? A monolithic container? I'm not really sure how you guys want to split up the project.
I'm thinking 1 container for the frontend, 1 container for the api, 1 container for the DB. Frontend would just talk via REST or WS to the API, and the API would talk to the DB via ambassador link.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/Kegstarter/kegstarter/issues/5#issuecomment-226051120, or mute the thread https://github.com/notifications/unsubscribe/AA5zNeqwJWrOFCC5s1TG4SvAah4CwRABks5qLz82gaJpZM4CMML3 .
Putting things in containers isn't just for scale, but I get you're train of thought. The app is pretty simple, but I thought we were going to use this for learning/experimentation.
If you don't want to split the app you can use containers as a drop in replacement for a VM if you really wanted to. In the case of PR #6, I'm doing just that, the container is just acting as a Ubuntu VM. You can choose not to use it, but it's a nice tool that gives you a lot of config for free.
probably. I want to play with it soon, but I think it's a good path forward.