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:

๐—–๐—ต๐—ผ๐—ผ๐˜€๐—ถ๐—ป๐—ด ๐˜๐—ต๐—ฒ ๐—ฅ๐—ถ๐—ด๐—ต๐˜ ๐—ฆ๐˜๐—ผ๐—ฟ๐—ฎ๐—ด๐—ฒ ๐—ข๐—ฝ๐˜๐—ถ๐—ผ๐—ป ๐—ถ๐—ป ๐—ข๐—–๐—œ ๐—ณ๐—ผ๐—ฟ ๐—˜๐—•๐—ฆ ๐—”๐—ฝ๐—ฝ๐—น๐—ถ๐—ฐ๐—ฎ๐˜๐—ถ๐—ผ๐—ป๐˜€

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

Recommended Posts

Start typing and press Enter to search