My writing backlog includes a post defining what "good" looks like for a web service. I don't think most organizations are doing it well, or have their priorities straight.
Rumor has it that there is a 30+ page checklist if you work at AWS and want to launch a new service. Meanwhile, CloudFormation support still trails most new service launches and remains completely unavailable for many old services. These things suggest strongly that they are coding the area, not the perimeter.
In many ways, AWS's insistence on proprietary vs. universal open-source and the lack of interoperability with other cloud providers is itself "coding the area", turning an O(N+M) problem into an O(N*M) one.
AWS's console UI is a pretty good sign of "coding the area" as well. So many subtle inconsistencies in the UI with navigation structure, pagination, filtering/search with all of their different services.
My writing backlog includes a post defining what "good" looks like for a web service. I don't think most organizations are doing it well, or have their priorities straight.
Rumor has it that there is a 30+ page checklist if you work at AWS and want to launch a new service. Meanwhile, CloudFormation support still trails most new service launches and remains completely unavailable for many old services. These things suggest strongly that they are coding the area, not the perimeter.