Service Level Agreement (SLAs) restrictions and specifications are essentially cloud-based architectural requirements. Cloud-based system architects face the challenge of aligning service level agreements (SLAs) with the architecture and delivery of services, whether functional or non-functional. Any violation of these agreements with respect to performance, availability, reliability, security, compliance, etc., may result in damage to the supplier`s reputation or penalties in the form of cash or in-service credit refunds . From now on, architecture will become a „strategy game“ and a challenge in which architects will have to make cost-effective and efficient decisions, anticipate the risks and the value of these decisions against probable or unpredictable changes in requirements and operating environments. This leads to a design process focused on service level agreements and oriented towards value, for operation and evolution, where the orientation of business objectives and technical pilots is at the heart of the process. Architectural design decisions aim to ensure that ASA violations can be reduced by ensuring that critical requirements are made available through reliable resources. That`s why the challenge arises as to what architectural strategies, tactics, and styles could help cloud providers meet the dynamic requirements of cloud-based systems while meeting service-level conditions. Aspects of the ALS lifecycle, such as Service Discovery, SLA negotiation and coordination, monitoring and reporting, can be comparable to architectural tactics and components that meet these objectives. A service level agreement (SLA) is an obligation between a service provider and a customer. Particular aspects of the service – quality, availability, responsibilities – are agreed between the service provider and the service user.  The most common component of an SLA is that services must be provided to the customer as contractually agreed.
For example, Internet service providers and telecommunications companies will typically include service level agreements in the terms of their contracts with customers to define the service level(s) sold in plain language. In this case, the SLA usually deconstructs a technical definition in the intermediate period between failures (MTBF), average repair time or mean recovery time (MTTR); identification of the party responsible for reporting errors or paying fees; responsibility for different data rates; throughput; Jitter; or other similar measurable details….