|
Hi [subscriber:firstname | default:subscriber],
|
This is OCI newsletter #6.
|
Let's talk about Regions, Availability Domains and Fault Domains this week! And a bit about networking.
|
Feedback is always valued! Contact me via Twitter @svilmune or just send an email if you have any ideas or comments.
|
I had a good discussion about this and the second newest region in Canada, ca-toronto-1. Both regions have currently only one Availability Domain so you need to take this into account if you plan on using them and have possible requirement to use multiple ADs in the future.
|
You can find documentation and best practices which mention you should always design for Availability Domain failure and if that's not possible then at least use different Fault Domains where hardware and infrastructure is grouped into different domains within Availability Domain.
|
If you then design for region failure this adds another level of complexity due to how services are build and how services can be shared within regions versus ADs. But sometimes this is required by your business as well!
|
Seriously though, these pillars are really good to guide even smaller companies building secure and reliable solutions. Just remember to give them a look at least! I also like Oracle has jumped to promote openness within OCI, could it guide some new customers to OCI as well in the long run?
|
What I see in many of these labs is you build the basic networking yourself. Wouldn't it be nice if you would just run the OCI resource manager package to have it pre-build? But I guess it's good to do VCN setup yourself so you get basics for that as well!
|
I'm not in partnership with Oracle in any way so all opinions are my personal views and should not be taken as an official statement from Oracle.
|
You can unsubscribe at any time using the link below if you feel this newsletter is not for you.
|
Hope you have a great day and thanks for reading!
|
|
|
|
|
|