Founder here, happy to answer any questions

I think the interesting opportunity here is can bring this real-time workflow to professional software teams that use git and micro-services?

The blog post talks about how the api server was dropping web hooks, and there is no re-try mechanism built into most web hook senders.

Scaling out an api server is not resilient enough, and there needs to be a queue-based system fronting your web hooks so they aren't dropped

Yes, but the title implies that they will stop using or supporting webhooks. A more accurate title would be "Handling Dropped Webhooks"

This is pretty cool, how does this integrate with the UX?

Hey @yKumar6,

This is automatically integrated within your prototypes. You can record and analyze all data-points just by sharing your prototypes over link... :)

Travis CI and Circle CI push code to a staging or production environment. So you still need to setup a full-stack environment to do end-to-end testing.

Runnable let's you have end-to-end (full-stack) environments with every branch. The minute a branch comes up, you have an environment. This includes a clone of your database

Founder here - We absolutely can! Just give us a heads up so we can make sure it loads up properly on your account

The reason it's built for Github organizations is we can access-control your private infrastructure based on the permissions set in Github.

We don't have access to the same APIs with just a personal accout

It's on our roadmap. Can you submit a support ticket and I can fill you in over email

Founder here. Check us out for your future jobs. Maintaining sandbox infrastructure is a pain.

One of our key lessons is being able to dispose and rebuild your infrastructure on a daily or weekly basis so leaks don't destroy your environment.

We recycle customer environments in Runnable, on a regular basis and its completely transparent to users

We're trying to hire developers to help us do that :-)

What's your stack like? For those interested...

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/

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?

What is your experience with using Docker Swarm in a production environment? I have heard conflicting views regarding it.

Responded in another thread here: https://news.ycombinator.com/item?id=11306045 Will be happy to go into more detail.