1002 IT Professionals from Infrastructure and related technologies
Only 82% were multi-cloud the year before
Hybrid was only 71% the year before
Only 1% of companies have no cloud strategies planned.
SaaS will be controlled, often by the original vendors that can lock customers into their cloud platform.
SAP = Hana. Azure = Microsoft, Linkedin, Slideshare…. Oracle=EBS, Peoplesoft, OBIEE. Amazon is taking large chunks out of each.
Amazon and Azure own this race, but a price war could shake up the future of which cloud our data resides.
Almost 70% of the market is owned by Amazon and Microsoft- Azure doubles each year, up 93% in 2016, expected $20 billion for 2018
During Amazon S3 outage, it wasn’t Azure or Oracle that benefited, but Google, which increased its business over 12% in just two days.
Over 80% of time is waiting for RDBMS, (relational databases) to be refreshed. Developers and Testers are waiting for data to do their primary functions.
This allows for faster and less costly migrations to the cloud, too.
If each deployment was packaged as a container, allowing different combinations, as needed for different tiers, to be developed, tested and released, as well as rolled back together, including data.
Without the developers knowledge or space usage for Flashback, backups to disk or tape recovery, what is the most common request?
Background processes, if multi-tenant, then you’ll have the CDB with VDBs all virtual.
Redo logs are almost all of the local storage.
Recovery the data from the database, the app code, the unstructured data, everything…
DEMO!!!!!***********************
DEMO!!!!!**********
Using a database VDB as an example….
You can add as many as the engine can handle the resources for- storage is quite minimal per VDB.
This includes the ways your data loads and sends data, as well.
I can not only migrate these to a single cloud, but mulitple ones. Keep in mind- no matter how many of these environments I need, I can have a single gold copy on the cloud and “pointers”, with VDB, projection to NFS mounts for structured/unstructured data, as well as applications. This saves considerably on cloud storage and the need to process data to multiple environments. Do it once, reuse it. Yet each is a read and write copy of the original gold copy.
Or does it shift the problem toward authentication and authorization?
Or does it shift the problem toward authentication and authorization?
Completely secured before it ever leave on-prem. The data can also be sent masked to unstructured or structured files, depending on the configuration, but obfuscated to ensure protection, non-reversible.