Clarification about ESLZ design principle

[TarekNabeel]

I need more clarification about the design principle "Application-centric and archetype-neutral" , what is actually meant by "application-centric" and "archetype-neutral" as acronyms and also i need an example of this principle if possible.

[jtracey93]

Hey @TarekNabeel,

Have you seen https://docs.microsoft.com/azure/cloud-adoption-framework/ready/enterprise-scale/design-principles#application-centric-and-archetype-neutral ?

[TarekNabeel]

@jtracey93 , thanks yes i wen through it but still not clear

[jtracey93]

Okay cool.

Effectively it means that ALZ/ESLZ doesn't lean towards supporting an IaaS only or PaaS only model, it supports both as it is agnostic to the type of workload.

It also is about focussing on the application and supporting it and its teams with what they need to move quickly by enabling their autonomy by configuring the ALZ/ESLZ platform in such a way - e.g. policy-driven governance.

Does this help @TarekNabeel?

[TarekNabeel]

@jack , apologies for late response and many thanks for the clear clarification.

…

On Wed, 13 Apr 2022, 09:46 Jack Tracey, ***@***.***> wrote: Okay cool. Effectively it means that ALZ/ESLZ doesn't lean towards supporting an IaaS only or PaaS only model, it supports both as it is agnostic to the type of workload. It also is about focussing on the application and supporting it and its teams with what they need to move quickly by enabling their autonomy by configuring the ALZ/ESLZ platform in such a way - e.g. policy-driven governance. Does this help @TarekNabeel <https://github.com/TarekNabeel>? — Reply to this email directly, view it on GitHub <#954 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYURQZLOLBR7IS2J3YC3XCLVEZ3VDANCNFSM5TAPRCUA> . You are receiving this because you were mentioned.Message ID: ***@***.***>