This does not sound like a Spark problem -- doesn't even necessarily sound like a distributed problem. Are you of a scale where building simple logic in a web tier that queries a NoSQL / SQL database doesn't work?
If you are at such a scale, then it sounds like you're describing a very high volume of small, very low latency queries. Spark is not designed for that. However it could do some crunching in the background and feed a serving layer technology like a NoSQL store with recent results, for example. On Wed, Feb 18, 2015 at 3:23 PM, Ralph Bergmann | the4thFloor.eu <ra...@the4thfloor.eu> wrote: > Hi, > > > Am 18.02.15 um 15:58 schrieb Sean Owen: >> That said, it depends a lot on what you are trying to do. What are you >> trying to do? You just say you're "connecting" to spark. > > There are 2 tasks I want to solve with Spark. > > 1) The user opens the mobile app. The app sends a pink to the backend. > When this happens the backend has to collect some data from other server > via http and has to do some stuff with this data. > > 2) The mobile app can download this data from 1. In this case the > backend has to find/create the right data (depending on user location, > rating, etc.) > > > Ralph > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
