In this article, we’ll explore some of the drawbacks we found with Postgres and explain the decision to build Schemaless and other backend services on top of MySQL.

Managerial mistakes that inhibit value exchange or network effects can kill a platform. Let’s look at the key errors.

With new hacking techniques, malware, viruses and threats being created faster than Melisandre’s demon babies, the web is indeed dark and full of terrors. Here are seven lessons for security managers pulled straight out of Westeros.

In this post I’ll explain why I think Uber’s article must not be taken as general advice about the choice of databases, why MySQL might still be a good fit for Uber, and why success might cause more problems than just scaling the data store.

Many examples in functional programming assume that you are always on the “happy path”. But to create a robust real world application you must deal with validation, logging, network and service errors, and other annoyances.

I have been fortunate to lead product at several companies. When I think about my experiences — both the shining moments and the tough days — I recognize a pattern.

Since we started breaking our monolith and introduced a microservices architecture we rely a lot on synchronous request-response style communication. In this blog post we’ll go over our current status and some of the lessons we learned.

Stripe, a company offering a suite of online payment APIs, quickly realized that their product’s value hinged on people’s ability to learn and understand how its API works.

By now, forward-thinking system architects are starting to realize that moving to a microservices architecture requires an entirely new set of monitoring tools.

There is a lot of evidence to suggest that users who are required to change their passwords frequently select weaker passwords to begin with, and then change them in predictable ways that attackers can guess easily