Use memcache to avoid hitting datastore and to make operations faster.

Now that profiles are always on cache, instead of making user-facing requests take longer time, the API behavior should be:

1. For a never-seen profile, instead of fetch basic info, return a 202 Accepted status code, and schedule the full sync in background task queue. Return the estimated time the result will be ready (can be hard coded as of now to 5s).
2. For cached profiles, if cache is expired (i.e., < 24hs), schedule a full sync in background with a named task to avoid overload.

Now that we have a periodic check of cached profiles every 6hrs, we can rely on that periodic updates to provide properly updated info, and make response-times of user-facing request a constant (<100ms).

This is a sample, valid profile page that never gets loaded up: https://swgoh.gg/u/miamizalandas/

From logs, it failed to load the arena team, but there is no arena team!

Reloading profile (fullUpdate=true)
Loading profile miamizalandas
Not found on memcache, fetching from datastore (err=memcache: cache miss)
Loading arena team ...
Unable to reload profile: swgohgg: profile miamizalandas may not have Commander Luke Skywalker activated. (err=swgohgg: unable to find collection for profile 'miamizalandas')

It may be a good idea to merge the Collection and Stats fields and to expand the Ship collections with the unit stats extracted. This way the Profile.Collection[0] contains all info at once. This requires a rework on the github.com/ronoaldo/swgoh/swgohgg package to merge the same info.

One option is to make the a new Character.Stats and Ship.Stats attribute to hold the info, and make it optional in the response JSON.

Return basic stats for all profiles that belong to a given Guild.

GET on the guild endpoint could return all 50 profiles in that guild. A new Guild field could be added to make this request faster.

GET on the guild endpoint, if there are no profiles in that guild, could then fetch the guild page, parse all profiles in there and schedule a profile sync for each one.

The current profile endpoint, /v1/profile/username, could be reworked to allow batch get / filter when no username is specified.

New /v1/profile/ endpoint that can return a list of profiles with the filter criteria via query string values:

• ?profile=user1&profile=user2...&profile=user3: return the specified profiles back.
• ?guild=guild1: return profiles from the specified guild name.

If no query string values are specified, return an empty result.

To some extent, this proposal returns an unidimensional array equivalent of the current api for the first filter when only one profile is set.