Couchbase & HPCC Systems – A complete mobile & data platform in the enterprise

Editor's Notes

• #3: Long time ago ice was seasonal and regional, lets call it Ice 1.0. Ice 2.0 is the centralization of ice near big cities and delivered to homes. Do you know what ice 3.0 is? A: ice by a push of a button in your home and hand. Do you know what the main reason why ice 1.0 , ice 2.0 and ice 3.0 happened? A: people tend to over think it but its simple ”people want ice” If we apply the same example to our industry it would look like this: main frames , centralized servers in data centers and mobile And the main reason why this happened is like before simple because “people want data” The future is NOT getting a more powerful horse that eats less hay and then selling ice at a 5% discount. The future is making the jump from 1 to 2 and then the jump from 2 to 3. But most people do not make the jump because they define themselves by “WHAT” they do instead of focusing on the larger driver, the ice
• #4: I’ve always saw things as a series of over lapping curves.
• #7: So let’s take a look at a typical homegrown mobile application platform. You have your database tier, where your systems of record live, most likely with a cache on top of those. And you have the intranet network layer, and security on top of both. Next you have your middle tier, where your web services live, and the internet network layer, and security on top of both. And last you have your client tier, the place where the devices themselves are, that’s your mobile phones, tablets, wearables, etc. And security on top of that. All of these devices need to move data to the database tier, over the internet. Most likely that’s via RESTful services. All of which you have to build and manage. So this is what Connected Apps look like today. Looking at this holistically, you have separate technologies and integrations you have to build, manage, and piece together. You have to build web services, manage client databases, handle all of the integrations, build out your database tier, and manage the security policies separately across all of these tiers. You can see that a homegrown mobile application platform is complex to build and manage. Syncing data from devices all the way to the cloud is hard to build and manage. Apps may or may not work offline in this scenario, and most of the time you have to custom-build your data API’s to integrate with existing systems. So wouldn’t it be better to have a solution that solves all of these challenges for you?
• #10: Couchbase helps business transform but How do you do that? WHAT: We support what people call an Engagement Database. It’s a memory first architecture which is built on a single simplified data platform.