Book Image

Oracle Cloud Infrastructure for Solutions Architects

By : Prasenjit Sarkar
Book Image

Oracle Cloud Infrastructure for Solutions Architects

By: Prasenjit Sarkar

Overview of this book

Oracle Cloud Infrastructure (OCI) is a set of complementary cloud services that enables you to build and run a wide range of applications and services in a highly available hosted environment. This book is a fast-paced practical guide that will help you develop the capabilities to leverage OCI services and effectively manage your cloud infrastructure. Oracle Cloud Infrastructure for Solutions Architects begins by helping you get to grips with the fundamentals of Oracle Cloud Infrastructure, and moves on to cover the building blocks of the layers of Infrastructure as a Service (IaaS), such as Identity and Access Management (IAM), compute, storage, network, and database. As you advance, you’ll delve into the development aspects of OCI, where you’ll learn to build cloud-native applications and perform operations on OCI resources as well as use the CLI, API, and SDK. Finally, you’ll explore the capabilities of building an Oracle hybrid cloud infrastructure. By the end of this book, you’ll have learned how to leverage the OCI and gained a solid understanding of the persona of an architect as well as a developer’s perspective.
Table of Contents (15 chapters)
1
Section 1: Core Concepts of Oracle Cloud Infrastructure
Free Chapter
2
Chapter 1: Introduction to Oracle Cloud Infrastructure
7
Section 2: Understanding the Additional Layers of Oracle Cloud Infrastructure

Deep diving into Oracle functions

We will deep dive into a couple of topics before talking about event-based Oracle Function deployment.

First, let's discuss filesystem access within the Docker container where the function runs:

  • Function code running inside the Docker container has read access for all the files and directories within the filesystem.
  • Function code only has write access to the /tmp filesystem.

This means that when you write the code and want to perform a file operation, such as downloading a file inside the docker container, you need to make sure that you only download that file to /tmp.

Although this /tmp is writable, it has a size restriction, and it is proportionate to the amount of memory that you allocate to this function. If you allocate 128 MB of memory to the function, then you can get 32 MB of allowed space on your /tmp. For 256 MB of allocated memory, it will be 64 MB, for 512 MB of allocated memory, it will be 128 MB, and for...