Many of you have asked about the best storage options for a multi-node EBS setup involving a DMZ server with a public load balancer. Here are some insights and best practices for such configurations:
Previous Post:
http://staging.doyensys.com/blogs/%f0%9d%97%96%f0%9d%97%b5%f0%9d%97%bc%f0%9d%97%bc%f0%9d%98%80%f0%9d%97%b6%f0%9d%97%bb%f0%9d%97%b4-%f0%9d%98%81%f0%9d%97%b5%f0%9d%97%b2-%f0%9d%97%a5%f0%9d%97%b6%f0%9d%97%b4%f0%9d%97%b5%f0%9d%98%81/
When Shared Storage is Used
Pros:
[1] Reduced maintenance effort for both infrastructure and applications.
[2] Faster completion of ADOP actions.
[3] Easier patching of EBS Oracle Homes and WebLogic.
[4] Lower storage costs (Can you guess why?).
Cons:
[1]Sharing the same EBS binaries on the DMZ server increases the risk of corruption from malware attacks.
[2] Requires extra caution in firewall and network configurations to control and minimize vulnerabilities at the load balancer level.
We’ve crafted an optimal architecture for EBS on OCI that minimizes costs, enhances performance, and prioritizes security. This has been beautifully illustrated in the diagram shared in Rao’s post below.
“https://www.linkedin.com/embed/feed/update/urn:li:share:7279800150506545152“
