In Part III of this blog series, we continued to explore some of the key considerations when choosing the right database and framework for your real-time mobile app. Now, let’s dive deeper and take a look at the database as the puppeteer, as well as Puppet itself.
In Parts I and II of this blog series, we presented three possible categories that a typical real-time mobile app falls into, and started to take a look at the design choices for all three kinds of apps. Now, let’s continue to explore some additional considerations when it comes to choosing the right database and framework for your real-time app.
In the first part of this blog series, we kicked things off by taking a look at the three possible categories that a typical real-time app falls into. Now, let’s start to explore the design
If you’re a mobile app developer, I imagine you’re constantly feeling the pressure to quickly bring new apps to market and update them faster than ever before. The demand is only ramping up, with no
In our last post in the Definitive Guide to the Modern Database series, we examined three different trade-offs: In-memory vs. Disk-based; Scale-In vs. Scale-out, Consistent vs. Inconsistent; and SQL vs. NoSQL, “Classical” vs. “Modern.” Today let’s take a look at the final trade-off to consider when selecting a modern database.