Suitable Scenarios for Oracle Cloud Infrastructure Autonomous Transaction Processing - Serverless (ATP-S) Deployment

ACE.

Oracle Cloud Infrastructure (OCI) Autonomous Transaction Processing Serverless (ATP-S) is a managed database offering that is designed to provide high-performance, highly available, and scalable databases without requiring the user to manage any infrastructure. It is a fully managed database service that automatically scales the computing and storage resources based on the workload. The service can be used for various use cases, but there are certain scenarios where it is more suitable.

The three scenarios that are suitable for the use of Oracle Cloud Infrastructure (OCI) Autonomous Transaction Processing Serverless (ATP-S) deployment are as follows:

A. A manufacturing company is running Oracle E-Business Suite application on-premises. They are looking to move this application to OCI and they want to use a managed database offering for their database tier.

This scenario is suitable for OCI Autonomous Transaction Processing Serverless deployment because the company is already using Oracle E-Business Suite, which is an enterprise resource planning (ERP) system that relies heavily on a relational database. With ATP-S, the company can migrate their existing Oracle database to a managed database in OCI without the need to manage any infrastructure. ATP-S is designed to handle high-performance and highly available databases that can support critical business applications.

B. A midsize company is considering migrating its legacy on-premises MongoDB database to Oracle Cloud Infrastructure (OCI). The database has significantly higher workloads on weekends than weekdays.

This scenario is also suitable for OCI Autonomous Transaction Processing Serverless deployment because the company is considering migrating their MongoDB database to OCI, and ATP-S is a good choice for MongoDB workloads. ATP-S provides a fully managed MongoDB-compatible database service that automatically scales based on the workload. The company can take advantage of the serverless architecture of ATP-S to save costs during the weekdays and scale up on weekends when the workload is higher.

C. A small startup is deploying a new application for eCommerce and it requires a database to store customers' transactions. The team is unsure of what the load will look like since it is a new application.

This scenario is suitable for OCI Autonomous Transaction Processing Serverless deployment because the startup is deploying a new application and is unsure of the load it will generate. ATP-S provides a fully managed database service that automatically scales based on the workload. The startup can take advantage of the serverless architecture of ATP-S to ensure that they are only paying for the resources they need, and the database can scale up automatically when the load increases.

The other two scenarios are not suitable for OCI Autonomous Transaction Processing Serverless deployment:

D. A well-established, online auction marketplace is running an application where there is database usage 24x7, but also has peaks of activity that are hard to predict. When the peaks happen, the total activities may reach 3 times the normal activity level.

This scenario is not suitable for OCI Autonomous Transaction Processing Serverless deployment because the workload is 24x7 and has unpredictable peaks. ATP-S is designed for workloads that are intermittent, where the workload can scale down to zero. In this scenario, the database workload is continuous, and the company may be better off with a different OCI database service, such as Autonomous Transaction Processing (ATP) or Autonomous Database (ADB).

E. A developer working on an internal project needs to use a database during work hours but doesn't need it during nights or weekends. The project budget requires her to keep costs low.

This scenario is not suitable for OCI Autonomous Transaction Processing Serverless deployment because the workload is predictable, and the database is not required during nights and weekends. ATP-S is designed for workloads that are intermittent, where the workload can scale down to zero. In this scenario, the developer may be better off with a different OCI database service, such as the Autonomous Transaction Processing (ATP) or Autonomous Database (ADB) that provides