ISV Architecture

This is the 1st blog in a series of blogs regarding the ISV Validated Design. 

This blog series will contain the following topics

1. ISV Home Page
2. ISV Architecture Validated Design 
   • Requirements, Design, Solution
   • Life of a packet
   • High Availability (HA) Concepts
3. Core Implementation
   • Part 3A - OCI - Routing and Security Lists
   • Part 3B - OCI vRouter - OCI Shape, OS choices, VNIC and Secondary IP address creation
4. Failover Implementation – You can choose from the two options below for implementation
   • Part 4A - Linux Clustering with Pacemaker and Corosync
   • Part 4B - Linux Clustering with Keepalived (VRRP)
5. Operations
   • How to add a customer to an existing POD
   • How to create a new POD
   • References, key files and commands

Oracle offers a wide array of software and services. Oracle Cloud is an Infrastructure as a Service (IaaS) offering that is utilized by Oracle's customers. Some of these customers, known an Independent Software Vendors (ISVs) want to leverage the Oracle Cloud to host a "managed service" as a turnkey cloud based solution for their End-Customers. This works well out of the box if the ISV has a small set of customers. What happens if the ISV wants to scale to 40, 60, 100, or larger amounts of customers? In this blog series, we will review the requirements, design, implementation and operations to help ISV's scale out.

This blog series is intended to empower cloud network architects to implement a large scale design. There might be more than one way to solve the connectivity challenges presented by ISVs. This blog series will help you make some design choices to help you scale your Cloud Network

An Oracle solutions guide has also been published on this topic as well and can be found here: https://docs.oracle.com/en/solutions/design-infra-saas/index.html