Note : The news link below clearly mentioned that it's a "Press Release" document.
It implies that any professional in the world can read through, share across and publicly express their opinion on the same in order to foster a good tech review / discussion spree for the benefit of the wider global audience to create a much better technological / thought world.
Thus, my two cents of review on the same....
Since the past couple of years, the entirety of the IT world is thriving on a paradigm shift to the cloud based in-house implementation and field deployment models for their respective software suites / application portals and thus the world renowned, established database software system, the Oracle Database implementation too is on the go for a similar cloud based execution model for every given public and private cloud infrastructure from their respective providers as below.
[ AWS, GC, MSA and of course the OCI ]
What all does such an implementation could have in store for the existing and the new / prospective customer base and what could be the potential delta difference from a customer perspective so as to have an optimistic high throughput from the revamped in-cloud Oracle database systems.
1. For every given instance of their respective cloud environment, the in-cloud Oracle Database system too shall be equally lightweight and portable as that of their base image that runs the entire software stack.
2. For every given instance of their respective cloud environment, the in-cloud Oracle Database system too shall be equally interconnected and inter accessible to all the peer systems deployed in a given domain.
3. For every given instance of their respective cloud environment, the in-cloud Oracle Database system too shall be equally lesser costly because it shall be licensed on the model of 'to be charged as per the usage basis' (hourly, daily, weekly, monthly etc..)
4. For every given instance of their respective cloud environment, the in-cloud Oracle Database system too shall be, commonly usable / shared database instance amongst multiple applications deployed on multiple application servers being run by the base image.
5. For example, my team and I have deployed an enterprise web archive on the Web-logic portal of my chosen cloud instance and my peer groups / teams have deployed the same or a similar enterprise web archive on a Web-sphere or SAP or JBoss or Glassfish or a given custom in-house application server's portal, then all of them can share a single instance of an in-cloud Oracle Database system without being bothered about any third party connectivity medium by relying on the universal Oracle JDBC connectivity enabled on the respective app server systems present in a given domain.
6. One of the most important concepts of patching an active / up and running in-cloud Oracle Database system shall be butter smooth with minimal downtimes / hosted application unavailability, because it shall be now a concept of updating the base image being run on all the containerised Oracle DB instances and spin up a new instance once the new image is up an running.
ADOP shall be now ADCP with the ease of cloud based availability for the same.
7. Thus, on par with the several ubiquitous merits of any given in-cloud software system, the in-cloud Oracle Database system too shall be the most happening software in the tech world out there for all the seamless feature rich experience provided to the users / customers / consumers.
8. For the applications hosted on the ones other than the native OCI instances, an additional requirement shall be to establish a clear dedicated group of ports for the universal connectivity to ensure that no other external applications are using the same set of ports inadvertently.
Many congratulations and best wishes to the world wide new age in-cloud Oracle Database systems for their successful implementation spree across a range of systems, consumers, customers, industries, and all other custom varied implementations... 💐🙂
No comments:
Post a Comment