2 added 126 characters in body
source | link

Yes, it makes sense to have one instance with multiple schemas/users (one per application, or whatever else).

Why? Oracle licenses are extremely expensive. You're wasting money (and wasting resources, honestly) if you have one instance per application. Unless you need them separated due to some business/PCI rule, you should be okay with multiple applications on one instance.

However, you should not be mixing prod/dev/qa environments within one instance.

Yes, it makes sense to have one instance with multiple schemas/users (one per application, or whatever else).

Why? Oracle licenses are extremely expensive. You're wasting money (and wasting resources, honestly) if you have one instance per application.

However, you should not be mixing prod/dev/qa environments within one instance.

Yes, it makes sense to have one instance with multiple schemas/users (one per application, or whatever else).

Why? Oracle licenses are extremely expensive. You're wasting money (and wasting resources, honestly) if you have one instance per application. Unless you need them separated due to some business/PCI rule, you should be okay with multiple applications on one instance.

However, you should not be mixing prod/dev/qa environments within one instance.

1
source | link

Yes, it makes sense to have one instance with multiple schemas/users (one per application, or whatever else).

Why? Oracle licenses are extremely expensive. You're wasting money (and wasting resources, honestly) if you have one instance per application.

However, you should not be mixing prod/dev/qa environments within one instance.