Vendor Neutrality in the Evolving Landscape of Cloud Computing: Strategies, Challenges, and Implications

Abstract

In the modern IT landscape, cloud computing has become ubiquitous, with many organizations adopting multi-cloud or hybrid-cloud strategies. This shift necessitates a critical examination of vendor neutrality, particularly in domains like data backup, disaster recovery, and application deployment. This research report delves into the multifaceted aspects of vendor neutrality, exploring its benefits, challenges, and the strategies employed to achieve it. We analyze the trade-offs between vendor-specific solutions and vendor-neutral approaches, examining the impact on cost, data portability, compliance, and long-term strategic flexibility. The report also investigates the role of open-source technologies and emerging standards in facilitating vendor neutrality. Furthermore, we address the evolving landscape of cloud services and the increasing complexity of managing data and applications across diverse cloud environments. This report aims to provide a comprehensive understanding of vendor neutrality for IT professionals, cloud architects, and decision-makers navigating the intricacies of cloud adoption and management.

Many thanks to our sponsor Esdebe who helped us prepare this research report.

1. Introduction: The Rise of Multi-Cloud and the Need for Vendor Neutrality

The proliferation of cloud computing has fundamentally altered the IT landscape. Organizations are increasingly adopting multi-cloud strategies, leveraging services from multiple cloud providers (e.g., Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP)) to optimize performance, enhance resilience, and avoid vendor lock-in [1]. This approach allows businesses to select the best services for specific workloads, negotiate competitive pricing, and distribute risk across different providers. However, the benefits of multi-cloud adoption are contingent upon effectively managing the inherent complexities of disparate platforms, APIs, and management tools.

Vendor lock-in, a long-standing concern in the IT industry, is amplified in the cloud era. Reliance on a single cloud provider can create dependencies that are difficult and costly to break, limiting an organization’s ability to switch providers, negotiate better terms, or adopt innovative technologies from alternative vendors [2]. This dependence can hinder agility, stifle innovation, and ultimately increase the total cost of ownership. Therefore, vendor neutrality has emerged as a crucial consideration for organizations seeking to harness the full potential of multi-cloud environments.

Vendor neutrality, in this context, refers to the ability to deploy, manage, and migrate applications and data across different cloud platforms without being tied to the proprietary technologies or formats of a specific vendor [3]. It encompasses a range of strategies, including the use of open standards, vendor-agnostic tools, and architectural patterns that promote interoperability and portability. Achieving vendor neutrality requires careful planning, strategic technology choices, and a commitment to avoiding vendor-specific dependencies.

The stakes are high. A successful vendor-neutral strategy can unlock significant advantages, including increased agility, cost savings, enhanced data portability, and improved compliance. Conversely, failure to address vendor lock-in can lead to increased costs, reduced flexibility, and potential competitive disadvantages.

Many thanks to our sponsor Esdebe who helped us prepare this research report.

2. Benefits of Vendor Neutrality in Cloud Environments

The adoption of a vendor-neutral approach in cloud environments offers a plethora of benefits, contributing to improved agility, cost efficiency, and long-term strategic flexibility. These advantages can be categorized into several key areas:

• Cost Optimization: Vendor neutrality allows organizations to negotiate competitive pricing with cloud providers. By avoiding dependence on a single vendor, businesses can leverage competitive pressure to secure better deals. Furthermore, it enables the optimal placement of workloads based on cost considerations, allowing organizations to move applications and data to the most cost-effective platform at any given time [4]. This dynamic optimization can result in significant cost savings over the long term.

• Enhanced Agility and Flexibility: Vendor-neutral architectures facilitate faster application deployment and easier migration between cloud environments. This agility enables organizations to respond quickly to changing business requirements and adapt to new technological opportunities. It also reduces the risk associated with relying on a single vendor’s roadmap and allows organizations to adopt innovative technologies from different providers [5].

• Improved Data Portability: Vendor neutrality ensures that data can be easily moved between different cloud platforms without significant transformation or compatibility issues. This portability is crucial for disaster recovery, business continuity, and data sovereignty compliance. By avoiding vendor-specific data formats and storage solutions, organizations can maintain control over their data and avoid being locked into a particular provider’s ecosystem.

• Reduced Vendor Lock-in: This is perhaps the most cited benefit. Vendor neutrality mitigates the risk of vendor lock-in, preventing organizations from becoming overly dependent on a single cloud provider. This independence allows businesses to switch providers, negotiate better terms, and avoid being held hostage by proprietary technologies. It also promotes innovation by encouraging vendors to compete on merit rather than through artificial barriers to entry [6].

• Increased Resilience and Disaster Recovery: A vendor-neutral approach facilitates the implementation of robust disaster recovery strategies. By replicating data and applications across multiple cloud providers, organizations can ensure business continuity in the event of an outage or disaster affecting a single provider. This distributed architecture enhances resilience and minimizes downtime [7].

• Simplified Compliance: Vendor neutrality can simplify compliance with data privacy regulations, such as GDPR and CCPA. By avoiding vendor-specific data residency requirements and ensuring data portability, organizations can maintain control over their data and comply with evolving regulatory requirements. This control is essential for protecting sensitive information and maintaining customer trust [8].

Many thanks to our sponsor Esdebe who helped us prepare this research report.

3. Challenges in Achieving Vendor Neutrality

While the benefits of vendor neutrality are compelling, achieving it is not without its challenges. Several factors can hinder organizations in their pursuit of a vendor-neutral cloud strategy:

• Technical Complexity: Building and maintaining vendor-neutral architectures can be technically challenging. It requires expertise in multiple cloud platforms, open standards, and vendor-agnostic tools. The integration of disparate systems and the management of data across different environments can be complex and time-consuming [9].

• Lack of Standardization: Despite the efforts of standards organizations, the cloud landscape remains fragmented, with variations in APIs, data formats, and management tools. This lack of standardization can make it difficult to achieve true vendor neutrality and requires careful planning and execution [10].

• Vendor-Specific Services and Features: Cloud providers often offer unique services and features that are not available on other platforms. These vendor-specific offerings can be tempting, but they can also lead to vendor lock-in. Organizations must carefully evaluate the trade-offs between leveraging vendor-specific features and maintaining vendor neutrality [11].

• Data Gravity: The concept of data gravity suggests that applications tend to gravitate towards the data they need to access. This phenomenon can make it difficult to move data between cloud environments, particularly when dealing with large datasets. Overcoming data gravity requires careful planning and the use of appropriate data transfer technologies [12].

• Skills Gap: Building and managing vendor-neutral cloud environments requires a specialized skillset that is often in short supply. Organizations may need to invest in training and development to equip their staff with the necessary skills [13].

• Management Overhead: Managing applications and data across multiple cloud environments can increase operational complexity and overhead. Organizations need to implement robust monitoring, automation, and governance tools to effectively manage their multi-cloud deployments [14].

• Cost of Abstraction: Achieving vendor neutrality often involves implementing abstraction layers or using vendor-agnostic tools. These tools can add to the complexity and cost of the overall solution. A careful cost-benefit analysis is needed to determine the optimal level of abstraction [15].

Many thanks to our sponsor Esdebe who helped us prepare this research report.

4. Strategies for Implementing a Vendor-Neutral Cloud Strategy

To overcome the challenges and realize the benefits of vendor neutrality, organizations can employ a range of strategies. These strategies can be broadly categorized into the following areas:

• Embrace Open Standards and APIs: Prioritize the use of open standards and APIs whenever possible. This includes standards for data storage, networking, and application development. Open standards promote interoperability and reduce the risk of vendor lock-in [16].

• Utilize Vendor-Agnostic Tools: Leverage vendor-agnostic tools for infrastructure management, application deployment, and data backup. These tools provide a consistent interface across different cloud platforms, simplifying management and reducing vendor dependencies [17]. Examples include Terraform for infrastructure as code, Ansible for configuration management, and Kubernetes for container orchestration.

• Adopt Containerization and Microservices: Containerization, particularly with Docker, and microservices architectures promote portability and flexibility. Containerized applications can be easily deployed across different cloud environments, and microservices architectures allow for independent scaling and updating of individual components [18].

• Implement Infrastructure as Code (IaC): Use Infrastructure as Code (IaC) tools to automate the provisioning and management of cloud resources. IaC allows you to define infrastructure in code, which can be versioned, tested, and deployed consistently across different cloud platforms. This approach promotes repeatability and reduces the risk of configuration errors [19].

• Choose Vendor-Neutral Data Formats: Avoid vendor-specific data formats and storage solutions. Use standard data formats, such as JSON or XML, and consider using object storage services that support open APIs, such as S3-compatible storage [20].

• Develop a Multi-Cloud Management Platform: Implement a multi-cloud management platform to provide a centralized view of your cloud resources and simplify management tasks. These platforms offer features such as monitoring, cost management, and security management across different cloud environments [21].

• Establish Clear Governance Policies: Define clear governance policies for cloud usage, including standards for security, compliance, and cost management. These policies should be enforced consistently across all cloud environments to ensure consistency and control [22].

• Adopt a Hybrid Cloud Strategy: A well-defined hybrid cloud strategy can promote vendor neutrality by allowing organizations to run workloads on-premises and in the cloud. This approach provides flexibility and control over data and applications [23].

• Regularly Audit and Evaluate Cloud Dependencies: Conduct regular audits of your cloud dependencies to identify potential areas of vendor lock-in. Evaluate the trade-offs between using vendor-specific features and maintaining vendor neutrality [24].

Many thanks to our sponsor Esdebe who helped us prepare this research report.

5. The Role of Open Source Technologies in Vendor Neutrality

Open-source technologies play a critical role in enabling vendor neutrality in cloud environments. Open-source tools and platforms provide a foundation for building vendor-agnostic architectures, promoting interoperability, and reducing vendor dependencies. Here are some key areas where open-source technologies contribute to vendor neutrality:

• Container Orchestration: Kubernetes, an open-source container orchestration platform, has become the de facto standard for managing containerized applications in the cloud. Kubernetes provides a consistent platform for deploying and managing applications across different cloud environments, regardless of the underlying infrastructure [25]. Its vendor-neutral nature allows organizations to avoid being locked into a specific cloud provider’s container management service.

• Infrastructure as Code: Terraform, an open-source infrastructure as code tool, allows organizations to define and manage cloud infrastructure in a declarative manner. Terraform supports multiple cloud providers, enabling organizations to provision and manage resources across different environments using a single tool [26].

• Configuration Management: Ansible, an open-source configuration management tool, automates the configuration and management of servers and applications. Ansible supports multiple operating systems and cloud platforms, allowing organizations to manage their infrastructure consistently across different environments [27].

• Monitoring and Logging: Open-source monitoring and logging tools, such as Prometheus and Elasticsearch, provide a comprehensive view of system performance and application behavior. These tools can be used to monitor resources across different cloud environments, providing valuable insights into performance and availability [28].

• Data Management: Open-source databases, such as PostgreSQL and MySQL, offer vendor-neutral alternatives to proprietary database solutions. These databases can be deployed across different cloud platforms and provide a consistent data management layer [29]. Furthermore, projects like Apache Arrow provide a standardized, cross-language format for in-memory data, improving data portability.

• Serverless Computing: While serverless computing is often associated with vendor-specific platforms like AWS Lambda or Azure Functions, open-source projects like Knative aim to provide a vendor-neutral serverless framework that can be deployed on different cloud environments [30].

The adoption of open-source technologies is not without its challenges. Organizations need to have the expertise to deploy and manage these tools, and they need to be aware of the licensing implications of using open-source software. However, the benefits of vendor neutrality and interoperability often outweigh the challenges.

Many thanks to our sponsor Esdebe who helped us prepare this research report.

6. Vendor-Neutral Backup Solutions: A Case Study

Data backup is a critical aspect of any cloud strategy, and vendor neutrality is particularly important in this area. Organizations need to ensure that their data is protected against loss or corruption and that they can recover their data quickly and easily in the event of a disaster. Vendor-neutral backup solutions provide a way to achieve this without being locked into a specific cloud provider’s backup service.

Several vendor-neutral backup solutions are available, each with its own strengths and weaknesses. These solutions typically offer features such as:

• Support for Multiple Cloud Platforms: The ability to back up data from different cloud environments, including AWS, Azure, and GCP.

• Centralized Management: A single console for managing backups across all cloud environments.

• Automated Backup Scheduling: Automated backup scheduling to ensure that data is backed up regularly.

• Data Encryption: Data encryption to protect sensitive information during backup and recovery.

• Fast Recovery: Fast recovery times to minimize downtime in the event of a disaster.

One approach to vendor-neutral backups is using storage-agnostic backup tools that write directly to object storage. Backups can be written into a standard format, like TAR or proprietary but widely supported formats, directly into S3-compatible storage [31]. This way you can change cloud providers that support object storage without having to change your backup strategy.

Another approach is to use a third-party backup service that supports multiple cloud platforms. These services typically offer a range of features, including automated backups, data encryption, and fast recovery times. Some examples of vendor-neutral backup solutions include Veeam, Rubrik, and Commvault.

The choice of a vendor-neutral backup solution will depend on the specific requirements of the organization. Factors to consider include the size of the data to be backed up, the recovery time objective (RTO), and the recovery point objective (RPO). It’s also important to evaluate the cost of the solution and the level of support that is provided.

Many thanks to our sponsor Esdebe who helped us prepare this research report.

7. Cost Implications of Vendor Neutrality

While vendor neutrality offers numerous benefits, its cost implications require careful consideration. The financial impact of adopting a vendor-neutral approach can be complex, encompassing both direct and indirect costs. A thorough analysis is crucial to determine the overall cost-effectiveness of a vendor-neutral strategy.

• Initial Investment: Implementing a vendor-neutral architecture often requires an initial investment in new tools, technologies, and training. This may include purchasing vendor-agnostic software, hiring specialized personnel, or investing in training programs to upskill existing staff. These upfront costs can be significant and should be carefully factored into the overall cost analysis.

• Operational Costs: Vendor-neutral environments can introduce additional operational complexities, potentially leading to higher ongoing costs. Managing multiple cloud platforms, integrating disparate systems, and maintaining vendor-agnostic tools can increase the operational overhead. Organizations may need to invest in automation and monitoring tools to streamline operations and minimize costs.

• Cost Optimization Opportunities: Despite the initial investment and potential operational complexities, vendor neutrality can unlock significant cost optimization opportunities. By avoiding vendor lock-in, organizations can negotiate competitive pricing with cloud providers and leverage spot instances or reserved instances to reduce costs. Furthermore, vendor neutrality enables organizations to optimize workload placement based on cost considerations, moving applications and data to the most cost-effective platform at any given time [32].

• Cost of Migration: Migrating applications and data between cloud platforms can be a costly undertaking, particularly for large and complex workloads. Vendor neutrality can simplify migration, reducing the cost and effort involved in moving applications and data between environments. This agility can lead to significant cost savings over the long term.

• Hidden Costs: It’s important to consider the potential hidden costs associated with vendor neutrality. These may include the cost of downtime during migration, the cost of rework due to compatibility issues, and the cost of managing vendor relationships. A comprehensive cost analysis should account for all potential costs, both direct and indirect.

• Long-Term Cost Savings: The long-term cost savings associated with vendor neutrality can be substantial. By avoiding vendor lock-in, organizations can maintain their flexibility and negotiate better terms with cloud providers. Furthermore, vendor neutrality enables organizations to adopt innovative technologies from different providers, potentially leading to further cost savings.

Many thanks to our sponsor Esdebe who helped us prepare this research report.

8. Impact on Data Portability and Compliance

Vendor neutrality has a significant impact on data portability and compliance, enabling organizations to maintain control over their data and comply with evolving regulatory requirements. Data portability refers to the ability to move data easily between different cloud platforms or between on-premises environments and the cloud. Compliance refers to adherence to legal and regulatory requirements, such as data privacy laws and industry-specific regulations.

• Enhanced Data Portability: Vendor neutrality enhances data portability by avoiding vendor-specific data formats and storage solutions. By using standard data formats and open APIs, organizations can easily move data between different cloud environments without significant transformation or compatibility issues. This portability is crucial for disaster recovery, business continuity, and data sovereignty compliance [33].

• Simplified Compliance: Vendor neutrality simplifies compliance by enabling organizations to maintain control over their data and comply with evolving regulatory requirements. By avoiding vendor-specific data residency requirements and ensuring data portability, organizations can comply with data privacy laws, such as GDPR and CCPA. This control is essential for protecting sensitive information and maintaining customer trust [34].

• Data Sovereignty: Data sovereignty refers to the concept that data is subject to the laws and regulations of the country in which it is located. Vendor neutrality enables organizations to comply with data sovereignty requirements by allowing them to store data in specific geographic regions. This control is crucial for organizations operating in multiple countries or regions [35].

• Data Governance: Vendor neutrality facilitates data governance by providing a consistent framework for managing data across different cloud environments. Organizations can implement centralized data governance policies and enforce them consistently across all environments. This consistency is essential for ensuring data quality, security, and compliance.

• Reduced Risk: Vendor neutrality reduces the risk of non-compliance by providing organizations with greater control over their data. By avoiding vendor lock-in, organizations can ensure that they can comply with evolving regulatory requirements without being constrained by the limitations of a specific cloud provider. This risk mitigation is crucial for protecting the organization’s reputation and avoiding potential fines or penalties.

Many thanks to our sponsor Esdebe who helped us prepare this research report.

9. The Future of Vendor Neutrality in the Cloud

The future of vendor neutrality in the cloud is likely to be shaped by several key trends, including the increasing adoption of multi-cloud strategies, the emergence of new technologies, and the evolving regulatory landscape. As organizations continue to embrace multi-cloud environments, vendor neutrality will become even more critical for maintaining agility, flexibility, and cost control.

• Increased Adoption of Multi-Cloud Strategies: Organizations are increasingly adopting multi-cloud strategies to leverage the best services from different cloud providers, optimize performance, and enhance resilience. This trend will drive the demand for vendor-neutral solutions and architectures [36].

• Emergence of New Technologies: New technologies, such as serverless computing, edge computing, and artificial intelligence, are reshaping the cloud landscape. These technologies will require vendor-neutral solutions that can be deployed across different cloud environments and integrated with existing systems [37].

• Evolving Regulatory Landscape: The regulatory landscape is constantly evolving, with new data privacy laws and industry-specific regulations being introduced regularly. Vendor neutrality will be essential for organizations to comply with these evolving requirements and maintain control over their data [38].

• Standardization Efforts: Efforts to standardize cloud APIs and data formats will continue to play a crucial role in promoting vendor neutrality. Standards organizations, such as the Cloud Native Computing Foundation (CNCF) and the Open Compute Project (OCP), are working to develop open standards that facilitate interoperability and portability [39].

• Rise of Cloud-Native Applications: The increasing adoption of cloud-native applications, built using microservices and containers, will further drive the demand for vendor-neutral solutions. Cloud-native applications are designed to be portable and scalable, making them well-suited for multi-cloud environments [40].

• Increased Focus on Data Governance: Data governance will become increasingly important as organizations grapple with the challenges of managing data across multiple cloud environments. Vendor-neutral data governance tools and frameworks will be essential for ensuring data quality, security, and compliance [41].

In conclusion, vendor neutrality is a critical consideration for organizations adopting cloud computing. By embracing vendor neutrality, organizations can unlock significant benefits, including increased agility, cost savings, enhanced data portability, and improved compliance. While achieving vendor neutrality is not without its challenges, the strategies and technologies outlined in this report provide a roadmap for success. As the cloud landscape continues to evolve, vendor neutrality will become even more important for organizations seeking to harness the full potential of cloud computing.

Many thanks to our sponsor Esdebe who helped us prepare this research report.

References

[1] Gartner. (2019). Gartner Says Worldwide Public Cloud Revenue to Grow 17.5 Percent in 2019. https://www.gartner.com/en/newsroom/press-releases/2019-04-02-gartner-says-worldwide-public-cloud-revenue-to-grow-17-5-percent-in-2019

[2] Armbrust, M., Fox, A., Griffith, R., Joseph, A. D., Katz, R., Konwinski, A., … & Zaharia, M. (2010). A view of cloud computing. Communications of the ACM, 53(4), 50-58.

[3] Mell, P., & Grance, T. (2011). The NIST definition of cloud computing. National Institute of Standards and Technology, 53(6), 50.

[4] Buyya, R., Ranjan, R., & Calheiros, R. N. (2010). Intercloud: Utility-oriented federation of cloud computing environments for scaling of application services. In Proceedings of the 10th International Conference on Algorithms and Architectures for Parallel Processing (ICAPP) (pp. 13-31). Springer, Berlin, Heidelberg.

[5] Weinhardt, C., Anandasivam, A., Binnig, C., Leimeister, J. M., & Stößer, J. (2009). Cloud computing–a classification, business models, and research directions. Business & Information Systems Engineering, 1(5), 391-399.

[6] Kreps, J. (2013). The log: What every software engineer should know about real-time data’s unifying abstraction. O’Reilly Media.

[7] Rimal, B. P., Choi, E., & Lumb, A. (2009). A taxonomy and survey of cloud computing systems. In Incite: Online Journal of Information Systems, 1(1), 5-26.

[8] Voas, J., & Zhang, J. (2009). Cloud computing: new business opportunities for the intelligence community. Computer, 42(1), 84-87.

[9] Dikaiakos, M. D., Katsaros, D., Mehra, P., Pallis, G., & Vakali, A. (2009). Cloud computing: Distributed internet computing for IT and scientific research. Internet Computing, IEEE, 13(5), 10-13.

[10] Sultan, N. (2011). Reaching for the cloud: How SMEs can manage. International Journal of Information Management, 31(3), 272-278.

[11] Jansen, W., & Grance, T. (2011). Guidelines on security and privacy in public cloud computing. National Institute of Standards and Technology.

[12] Copeland, D. (2017). Data gravity is the single biggest issue in cloud computing. https://www.computerweekly.com/blog/Data-Matters/Data-gravity-is-the-single-biggest-issue-in-cloud-computing

[13] TechTarget. (n.d.). Cloud skills gap. https://www.techtarget.com/searchcloudcomputing/definition/cloud-skills-gap

[14] Hayes, B. (2008). Cloud computing. Communications of the ACM, 51(7), 9-11.

[15] Erickson, R. (2011). Cloud vs. virtualization: What’s the difference?. Network World, 28(40), 16-17.

[16] European Commission. (2016). European Interoperability Framework (EIF) Implementation Strategy. https://ec.europa.eu/isa2/sites/isa/files/eif_implementation_strategy.pdf

[17] HashiCorp. (n.d.). Terraform. https://www.terraform.io/

[18] Newman, S. (2015). Building microservices: Designing fine-grained systems. O’Reilly Media, Inc.

[19] Willis, I., & Lebowsky, J. (2016). Infrastructure as code: managing servers in the cloud. O’Reilly Media.

[20] Amazon Web Services. (n.d.). Amazon S3. https://aws.amazon.com/s3/

[21] RightScale. (2019). 2019 State of the Cloud Report. https://www.flexera.com/resource-center/reports/2019-state-of-the-cloud-report/

[22] Cloud Security Alliance. (n.d.). Security Guidance for Critical Areas of Focus in Cloud Computing V4.0. https://cloudsecurityalliance.org/guidance/

[23] Hurwitz, J., Bloor, R., Kaufman, M., & Halper, F. (2010). Cloud computing for dummies. John Wiley & Sons.

[24] Carnegie Mellon University. (n.d.). Software Architecture: Architectural Tradeoff Analysis Method (ATAM). https://resources.sei.cmu.edu/library/asset-summary.cfm?assetid=8679

[25] Kubernetes. (n.d.). https://kubernetes.io/

[26] Terraform. (n.d.). https://www.terraform.io/

[27] Ansible. (n.d.). https://www.ansible.com/

[28] Prometheus. (n.d.). https://prometheus.io/

[29] PostgreSQL. (n.d.). https://www.postgresql.org/

[30] Knative. (n.d.). https://knative.dev/

[31] Amazon S3. (n.d.). What is Amazon S3. https://aws.amazon.com/s3/

[32] Spotinst. (n.d.). Cloud Cost Optimization. https://spot.io/

[33] The European Union General Data Protection Regulation (GDPR). (2016). Regulation (EU) 2016/679. https://gdpr-info.eu/

[34] The California Consumer Privacy Act (CCPA). (2018). Assembly Bill No. 375. https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201720180AB375

[35] KPMG. (2016). Data sovereignty: The cloud’s new frontier. https://home.kpmg/xx/en/home/insights/2016/07/data-sovereignty-the-clouds-new-frontier.html

[36] Flexera. (2022). 2022 State of the Cloud Report. https://www.flexera.com/resource-center/reports/2022-state-of-the-cloud-report/

[37] Weinman, L. (2019). Serverless computing. Addison-Wesley Professional.

[38] Cloud Security Alliance. (2021). Top Threats to Cloud Computing. https://cloudsecurityalliance.org/research/top-threats/

[39] Cloud Native Computing Foundation (CNCF). (n.d.). https://www.cncf.io/

[40] Richardson, C. (2019). Microservices patterns: With examples in Java. Manning Publications.

[41] DAMA International. (2017). DAMA-DMBOK: Data Management Body of Knowledge. Technics Publications.