Through years of partnering with clients and integrating our solutions into their existing tools, we’ve always found that a bit of flexibility can go a long way. That’s why we’ve built the upcoming Enterprise Edition of our streaming platform to have removable pieces. We know that there is never a one-size fits all solution when it comes to data needs, and it forces our own product team into some great practices to ensure that we support all of the edge cases we allow.
Recent posts by Andrew Murray
3 min read
8 min read
Introduced to the public in 2015, GraphQL came out of Facebook as the query language to power their transitioning of the mobile interfaces from web-based to native applications. Since then, it's been adopted by GitHub, Pinterest, Shopify and others to power their APIs.
The reason? There are many things that set GraphQL apart from RESTful APIs, but the main difference is that the requester has more control over exactly which parts of the response they want. Control and flexibility matter to us.
Topics: graphql product dev engineering
7 min read
Sometimes you need to play the short-game and roll out a solution to test its viability. When time is money, and you’re short on both, specific and ready-built solutions are a great way to get there in a hurry.
But if you are going for growth and the economies of scale, it’s worth the effort to plan ahead and look down the road. It can help prevent large cost and potential churn during the phase in your business when your client base is most critical.
11 min read
Or, how I used a deck of cards to protect my data.
Every year, our data becomes more accessible as the world is increasingly interconnected and more services we depend on become available online. This allows for ease that was unimaginable just twenty years ago. You can bank, apply for a mortgage and credit cards, share personal photos, store important documents and get a real-time view into your home at any time.