We have been pushing reactive microservices for some time now, but there are some considerations to take note of before taking the plunge. Reactive microservices bring a lot of benefits to the the table, but it comes at a cost. Here are some caveats that you should be aware of as you transition away from monoliths…
Keep reading
As a follow-up to our previous post on the versatility of Docker Compose, we wanted to emphasize how useful it can be to introduce Compose to your development workflow. Compose lets you take advantage of the benefits of Docker, while abstracting the complexity of your stack and of your Dockerfiles themselves. You may be used to running production images with Compose, but using it in development has benefits of its own.
Keep reading
We’re always trying to eliminate points of drop-off in our onboarding flow — we want to show value as quickly as possible to new users. Recently, we applied some unconventional methods to make this happen.
The first thing a user experiences in Runnable is our demo. Our app builds environments for git branches. We want users to see what that’s like right off the bat, so we start them off with a demo application. Since it’s tied to a repository on their own GitHub account, we can’t build it in advance, which means they have to wait for it to build.
Keep reading
A few months ago, Anand discussed the benefits of transitioning from traditional HTTP communication to event-driven microservices. He noted how this transition decoupled our services, forced scalable patterns, and increased our resilience. Here, we’ll detail the lessons we learned when we re-implemented our Cron-esque scheduler service, Khronos.
Keep reading
No matter how high your CTRs are on your advertising, it won’t translate into active users without an onboarding flow that helps users quickly understand the value of your product. This is what we’ve been focusing on now that Runnable is generally available. Here’s the approach we’ve been using to help more users “see the light”.
Keep reading
We rely heavily on Slack for communication throughout our company, so it was only a matter of time before we started utilizing Slack bots to improve our customer support workflows. With some light reading and a little programming, we’ve begun automating many mundane tasks which help us improve how we troubleshoot customer issues.
Keep reading