News for hackers. Stuff that matters.

A comment on Runnable Sandboxes: Full-stack environments for every GitHub branch. Parent comment

Re:Runnable Sandboxes: Full-stack environments for every Git... by kernel_panic on Thursday March 17, 2016 @01:12PM (#11305780)
Our stack is comprised of 15 stateless micro services all built with Nodejs. MongoDB, Redis and Neo4j are used for persistence, caching, and dependency management. The fundamental piece our system is RabbitMQ which is used as our event queue. The architecture designed around events. When an application dies or a commit is made, an event propagated through the system.

We also use a lot of open source software. Docker Machines + Swarm is used to schedule and run applications. Docker Registry is used to store images. We use WeaveWorkes weave for inter-container communication.

We are starting an engineering blog as well, keep posted for deep dives into our architecture! http://blog.runnable.com/

[ Parent | on HN ]
Re:Runnable Sandboxes: Full-stack environments for every Git... by bliti on Thursday March 17, 2016 @02:04PM (#11306251)
Interesting. I haven't worked a lot with Nodejs (Haven't really gotten to it), but have with the rest of the stack. I'm into messaging and networking. Maybe drop me a line?
[ Parent | on HN ]
Re:Runnable Sandboxes: Full-stack environments for every Git... by jmickey on Thursday March 17, 2016 @01:46PM (#11306125)
What is your experience with using Docker Swarm in a production environment? I have heard conflicting views regarding it.
[ Parent | on HN ]
Re:Runnable Sandboxes: Full-stack environments for every Git... by kernel_panic on Thursday March 17, 2016 @03:53PM (#11307065)
Responded in another thread here: https://news.ycombinator.com/item?id=11306045 Will be happy to go into more detail.
[ Parent | on HN ]