Keep track of Cloud Agnosticness
Read 1st article
Read 2nd article
Read 4th article
It took me a while to understand what would be the better approach going forward.
I also reviewed the idea of Cloud Agnosticness with my colleagues.
What we have until now is a way to measure the rating of Cloud Agnosticness.
How to continue from here?
Cloud Agnosticness rating is important because it tells you where you are on the path to Cloud Agnostic Architecture. This is the base for any decision.
Next, is when do we use the Cloud Agnosticness rating?
In the case that Cloud Agnostic architecture is important, I think that once in a while you need to check the Cloud Agnosticness rating.
I would suggest to do it before a major product event such as architecture addition or new software module development.
Evaluate the architecture for Cloud Agnosticness, simply because it is important, even if you do not plan any cloud migration yet.
Like any good navigator, an architect need to know the current position before continue in the path.
Enterprise Cloud Architect - Data & AI at Oracle
7 个月Super interesting Noam