Sometimes we want to export information from our datastore models to different storage technologies, with different capabilities.
A relational database is a good option if we need to create aggregation reports from our data, which in turn is really difficult to do directly from datastore, since it doesn’t support joins.
This guide shows how to keep datastore/yawp models in sync with Google Cloud SQL.
In this simple tutorial I’ll show you how to create a reactive API to automatically save products to the server as you type.
Since I’ve started mixing YAWP! APIs with some of the new Google Firebase 3.0 features, specially for my mobile apps, I’ve faced some challenges, mostly because the Firebase + Google Cloud integration is pretty new in the market.
YAWP! 1.5.0 is ready and it brings:
YAWP! 1.4.0 is ready to roll and, among other minor improvements, it brings:
Starting with version 1.4.0, to be released in a few days, YAWP! will enforce more strictly the semantic versioning scheme to indicate how changes affects its API.
Actually, you probably have had no problems so far, because we’ve been using a model very similar with only few differences.
This is the very first post on this blog!
From now on, this is where we will announce information about all the relevant releases of the framework, including new features, bugfixes, tips, usage examples and more.