#PostGresSQL conf 2016: #SQL vs #noSQL
Posted on April 18th, 2016
04/18/2016 @ New York Marriott Brooklyn Bridge
The afternoon panel was composed of vendors providing both SQL and noSQL database access. The discussion emphasized that the use of a #SQL vs #noSQL database is primarily driven by
- The level of comfort developers/managers have in a SQL or noSQL
- Whether the discipline in SQL rows and fields were useful in creating applications
- Whether applications use JSON structures which are easily saved in a noSQL database
- Linking to existing applications can be done either using a SQL database or using an ORM to a noSQL database.
The available of ORM (Object-relational mapping) software blurs the lines between SQL and noSQL databases. However, one is advised to avoid using an ORM when using a noSQL database initially so one can gain familiarity in the differences between SQL and noSQL.
Both db types need planning to avoid problems and depends on the situation. For instance, sharding might be best done late when there is only a single application being developed. However, if one has many applications using the same infrastructure, one should consider specifying sharding policy early.
People want to avoid complexity, but don’t want to delegate setup to a standard default or procedure.
Controlling access can be done (even if there is no data in the object) by creating views which are accessible only by some users.
Geolocation data is best handled by specialized db’s like CardoDB: The coordinate system is not rectangular and data can be handled by sampling and aggregation.
Beacons & Geolocation
Posted on November 7th, 2014
11/7/2014 @HelenMills space, 137 W 26th St, NY
Event sponsored by www.gimbal.com #beaconday14
Gimbal is an SDK and analytics platform for location-based mobile apps. Sessions were divided into technical walkthroughs for creating iOS apps and talks by vendors of apps using Gimbal’s services or providing infrastructure for targeting ads base on mobile location.
The two technical sessions showed how to use Xcode to construct apps with the Gimbal SDK. Geolocation apps are based on the following
- Location hardware which can be GPS (or other global systems) combined with finer grain services such as BTLE (blue tooth low energy) transponders.
- S-20 transponder which is palm size, takes regular batteries and transmits up to two years without changing batteries. Transmits Gimbal format and also beacon format
- S-10 (see picture) which is thumb size and works only for a few months on its battery. Transmits Gimbal format, but can be reprogrammed to transmit in beacon format.
- BTLE hardware to receive the signal. As of now only available on iPhone, but will be coming to Android phones with BTLE in early 2015
- Software: iOS Gimbal version 1 is released, but will be replaced by version 2 which is in beta. The v2 interface requires fewer software calls to the SDK. There is an Android SDK, but it is being revamped for OS 5.x which will be released in 2015. My understanding is that the current Gimbal Android SDK is primarily for use with geofence and does not work for geolocation. The software needs to smooth the inputs, create triggers for arrivals/departures, smooth the inputs for GPS and beacon, etc. The software maintains a list of beacon locations.
- Database software to create ad content, match to location information and determine the actions when users arrive or depart from locations.
- Analysis software to refine your use of the geolocation data.
Gary Damm and Sidd Panigrahi also described geofencing which is triggered by someone being within a boundary. They contrasted it with geolocation which emphasizes near location to a point in space.
Other presenters emphasized applications of geolocation.
Karen Pattani-Hanson & Megan Barry@UrbanAirship presented a case study at the US tennis Open. There 20 beacons covered the tennis center and were able to provide notifications that.
- Welcome first time visitor get welcome
- Featured activities – live streaming, US open radio, live prediction challenge
- Sponsorship monetization – e.g. esurance used iBeacon to identify people coming to the booth
- Sell last minute tickets – segment audience according to location and if on grounds, 32% click through rate
Dan Maxwell @VerveMobile talked about how Verve looks outside the store to drive traffic into the store – locate customers near the store, push inducement to go to the store, customize offers depending on location within the store. Their technology verifies that the customer entered the store and went to the part of the store. Also pops up a coupon once at that location in the store. Match to redemptions of the coupon
Antonio Tomarchio @Beintoo talked about building networks of beacons across different venues and locations and building a network of advertisers. The emphasized the importance of providing a trustworthy opt-in or opt-out mechanism
Anthony Dorment @Phigital talked about a tool that creates cards that to be displayed when triggered by a location arrival. Cards can include messages, media, video, user interaction, Google maps, etc. The goal is to make it easy to link content with the service to initiate it at a location.
Lior Nir @ShopAdvisor talked about a service across multiple vendors to alert customers to offers when they are near certain locations.
Brain Spracklen @SparkCompass talked about two case studies where geolocation data spurred user participation:
Case study #1- Ole Miss tries to encourage attendance at sports other than football. In the past needed to check in to get points. Replace by beacons. Encourage attendance once the program is announced. Also distributed to local merchants. In the future integrate with mobile payment and wearables to cut concession lines – place an order & you are sensed as you go to the concession and you are asked for your payment method.
Case study #2 – San Diego convention center – Comicon
Spark Compass will be coming out with a spark app in the next few weeks to program your own beacons and you own ads.
Toby @ControlGroup talked about some out-of the box uses for geolocation culminating in a demonstration of a companion robot – a mobile chair that can follow you (you’re your smart phone) using location sensors on the left and right arms.