Oracle Databaseの既存バージョンの10gや11gOracle Zero Data Loss Recovery Applianceの登場で、ますます重要な機能となってきたOracle Recovery Managerについて、OTN人気連載シリーズ「しばちょう先生の試して納得!DBAへの道」の執筆者が語ります。RMANバックアップの運用例から、高速増分バックアップの内部動作とチューニング方法まで、出し惜しみなく解説します。
This document discusses Oracle Management Cloud, which provides application performance monitoring, infrastructure monitoring, log analytics, and IT analytics services. It describes the services included in standard and enterprise editions, and provides pricing examples based on metrics like entities per hour and gigabytes per hour.
Oracle Databaseの既存バージョンの10gや11gOracle Zero Data Loss Recovery Applianceの登場で、ますます重要な機能となってきたOracle Recovery Managerについて、OTN人気連載シリーズ「しばちょう先生の試して納得!DBAへの道」の執筆者が語ります。RMANバックアップの運用例から、高速増分バックアップの内部動作とチューニング方法まで、出し惜しみなく解説します。
This document discusses Oracle Management Cloud, which provides application performance monitoring, infrastructure monitoring, log analytics, and IT analytics services. It describes the services included in standard and enterprise editions, and provides pricing examples based on metrics like entities per hour and gigabytes per hour.
ITアーキテクトのためのOracle Cloud Platform設計・構築入門 [Oracle Cloud Days Tokyo 2016]オラクルエンジニア通信
Oracle Cloud Days Tokyo 2016 (2016年10月開催)での講演資料です。
基幹システムなどの重要な企業システムに携わるアーキテクトにむけて、インフラや ミドルウェア配置だけではなくネットワークやセキュリティの考え方も含めた、Oracle Cloud Platformによる本格的なクラウド・システムの設計・構築ノウハウをギュッと凝縮してわかりやすくお伝えします。
成功事例に学べ! これからの時代のビッグデータ活用最新ベストプラクティス [Oracle Cloud Days Tokyo 2016]オラクルエンジニア通信
Oracle Cloud Days Tokyo 2016 (2016年10月開催)での講演資料です。
成功事例をご紹介すると同時に、 オラクルのビッグデータマネジメントシステムとアナリティクスソリューションをご紹介し、これからの時代に求められるビッグデータ活用のための最新ベストプラクティスをご紹介します。
This is a Quote with Picture slide ideal for including a picture with a brief quotation and attribution.
To Replace the Picture on this sample slide (this applies to all slides in this template that contain replaceable pictures)
Select the sample picture and press Delete. Click the icon inside the shape to open the Insert Picture dialog box. Navigate to the location where the picture is stored, select desired picture and click on the Insert button to fit the image proportionally within the shape.
Note: Do not right-click the image to change the picture inside the picture placeholder. This will change the frame size of the picture placeholder. Instead, follow the steps outlined above.
why polyglot persistence is an awful idea]j
One build on this slide.
Reminder that this slide gives the high level story without all the details. That would be for a follow-up visit/call with different materials and/or an expert.
[Note: The key point on this slide is that we can give the app developers what they want, which developers will of course be interested in. Distributed development imposes some costs on other parts of the organization which our approach helps with (right hand column after the build). Developers will often be less interested in this, (though some may appreciate the benefit of being able to query their data with SQL) but the rest of the organization will like it.]
Left hand side explanation.
Development today is often (not always, but often) about distributed app development. Basically this means separate teams moving at their own pace, using their own tools, languages, data model and database. One database per service is the norm, so with lots services come lots of potentially different databases. For developers this is great – they can do what the want, use what they want, and get things done faster. For everybody else, there are potential issues.
Oracle can support that model of development as well. But instead of different databases for each data model (see AWS list https://aws.amazon.com/products/databases/), we support lots of different data models in Oracle Database. So developers can fire up an Oracle instance to support their choice of JSON, Graph, key/value, relational or other data models. So we can give them what they want. But there’s more…
A developer using JSON might just use get/put to work with their data. They can do this of course, but they can do much more than that. Because this is based on a multi- model database, users are not restricted to just one way of accessing their data. So, for example, they could query that JSON data with SQL. Or use graph query to look for relationships. Another big benefit is that if the developer needs to change data models (they would hope not to, but it does happen) then with Oracle they get to keep the same database. With AWS they have to swap, and that is disruptive. So we can claim to support the development model that developers want, but with some advantages.
CLICK
On the other hand, the organization as a whole gets the benefit of centralized data when needed. Operational reporting, ad-hoc query, sercurity etc are all easier or better when done via Oracle Database than when done against a variety of different databases with different APIs, languages etc.
The exact details of how depends on which version of the database – on premises, in the cloud, autonomous or regular. Again, details for the next visit/call.
JSON – previously text rep, now also binary rep for 10x faster scans, 4x faster updates