Enterprises dream of hybrid applications across on-prem and public clouds. However, the cloud divide is real and inhibits enterprises from getting leverage in a hybrid cloud world. Join us for a conversation about how enterprises can unify their multiple clouds.

unfortunately restoring data with in the public cloud is slow and if it has to be restored on-prem can also be costly (due to egress charges). Technologies like StorReduce from @PureStorage can help reduce the time and costs associated with both restore types.

“That it just exists everywhere and quickly accessible.” Understanding zone/region design is critical for on-premises to public cloud success. Latency is your planning metric for cloud success on apps/services.

The greatest myth is that everything can be can processed in one cloud, without regard for latency, cost of moving data, and government/corporate compliance. Hybrid cloud bringing together distributed nodes is an essential evolution of enterprise computing.

#2 myth - Containers or VMs. It's both. Containers are cloud native and easier to move between clouds. VMs provide backwards compatibility - until enterprise apps are released as containers. MS SQL Server - now in a container. This will move some deployments out of VMs.

IMHO the strategy of moving "all your applications" to the Cloud (CTO/CIO mandate :) ) has gotten a reality check in the recent years. Capabilities available in the Cloud vs. on-prem are very different, which translates to on-prem, Cloud and hybrid apps that we see today

#3 myth - There is no such things as a steady state for IT. The faster you adopt cloud-native formats, the more fluidity your IT department will have an infrastructure and applications technologies advance.

May options!! on-prem Datacenter, co-locations, SaaS and multi-cloud available as platforms it is important to leverage the best of each of these platforms for your application needs. Building an application that can leverage the best of all worlds will be critical!!

One could take the explanation one step deeper by stating a hybrid application is a collection of disaggregated services - function, API, AI, compute, network, storage, etc - that is dynamic, extensible and spans multiple clouds.

I look at hybrid from less of an “application top down view” and more of an API focus. Design your application/service with independence in mind then you can deliver, hybrid, multi, etc. solutions. The focus on design the framework allows for ultimate flexibility.

@DeepStorageNet But what will be the basis for that collaboration? The goal is to benefit from separation. Orchestration technologies will be important, of course. But will data emerge as a glue that ties services together?

This design principle is straightforward for new application (or service) development. Cloud born, developed and scaled. Taking existing apps/services is a bigger challenge and converting to a micro or serverless model. Could mix on-premises APIs with Cloud APIs.

true - the micro services approach reduces the data required in terms of OS and app binaries - but that amount of capacity is minuscule compared to the capacity required to store the data being serviced, collected, etc by the app.

Everything must be fast..ideally silicon speed, non-stop, secure, shared, and deeply integrated w/ common orchestration frameworks like K8s, docker, rkt.. Intent based deployments for developers/devops to declare what attributes they want for their apps, builds + pipel

Essentially, this is what I call a "cellular" approach to building microservices with microdata. That requires a federation architecture at both the services and data levels, with the zones being federated going out to the edges.

@vStewed In many ways, this architecture requires automation of data storage/access through a pub-sub topic-oriented architecture in which microservices request and are provided with the most relevant data for which they've been permissioned.