{
"prompt": {
"label": "brief_resume",
"prompt": {
"prompt_id": "2",
"prompt_label": "brief_resume",
"content_format": "{\"data\": \"brief\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"point_1\", \"point_2\", ...] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "If the topic is not in English, translate it into English. \nSummarize with key points and simple words all the editorial guidelines provided to you: for example, a place, profession, theme, keyword.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\": \"brief\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"point_1\", \"point_2\", ...] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} If the topic is not in English, translate it into English. Summarize with key points and simple words all the editorial guidelines provided to you: for example, a place, profession, theme, keyword."
},
"content": "{\"data\":\"Understanding Cloud Native: Key Benefits and Practices \"}"
},
"response": {
"status": "ok",
"response": [
"Right then, 'Cloud Native' is all about building and running applications that take full advantage of the cloud computing model.",
"Key benefits include: faster development, improved scalability (easily handle more users), increased resilience (less downtime), and lower costs.",
"Important practices are: using containers (like Docker), microservices (breaking down apps into smaller bits), DevOps (developers and operations working together), and automation (doing things automatically, innit).",
"Basically, it's about making apps that are born in the cloud and thrive there, rather than just being shoved into it."
]
}
} {
"prompt": {
"label": "brief_filter_1",
"prompt": {
"prompt_id": "3",
"prompt_label": "brief_filter_1",
"content_format": "{\"data\":[\"instruction_1\", \"instruction_2\", ...]}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Remove the following topics from the provided list:\nSEO, natural referencing, duplication, backlinks, links, anchors, sponsorship, illustrations, images, word count, internal link, anchor, external link, original, unique, duplicated, AI, artificial intelligence, click, homepage, home, publication, linksgarden, approval, verification, category, no follow, do follow, link, guideline, guidelines, orphan, hierarchy, contextualize, copy-paste, proofread, bold, italic, bullet list, words, URL, site name, brand, name.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":[\"instruction_1\", \"instruction_2\", ...]} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Remove the following topics from the provided list: SEO, natural referencing, duplication, backlinks, links, anchors, sponsorship, illustrations, images, word count, internal link, anchor, external link, original, unique, duplicated, AI, artificial intelligence, click, homepage, home, publication, linksgarden, approval, verification, category, no follow, do follow, link, guideline, guidelines, orphan, hierarchy, contextualize, copy-paste, proofread, bold, italic, bullet list, words, URL, site name, brand, name."
},
"content": "{\"data\":[\"Right then, 'Cloud Native' is all about building and running applications that take full advantage of the cloud computing model.\",\"Key benefits include: faster development, improved scalability (easily handle more users), increased resilience (less downtime), and lower costs.\",\"Important practices are: using containers (like Docker), microservices (breaking down apps into smaller bits), DevOps (developers and operations working together), and automation (doing things automatically, innit).\",\"Basically, it's about making apps that are born in the cloud and thrive there, rather than just being shoved into it.\"]}"
},
"response": {
"status": "ok",
"response": [
"Right, 'Cloud Native' is all about crafting and running applications that properly leverage the cloud computing setup.",
"Top benefits include: quicker development, improved scalability (handling loads more users with ease), boosted resilience (less time offline, yeah?), and cheaper costs all round.",
"Key practices include: using containers (like Docker, see?), microservices (breaking apps down into smaller bits, like), DevOps (developers and operations mucking in together), and automation (doing things automatically, of course).",
"Basically, it's about creating apps that are born in the cloud and flourish there, instead of just being bunged into it as an afterthought, innit."
]
}
} {
"prompt": {
"label": "brief_filter_2",
"prompt": {
"prompt_id": "4",
"prompt_label": "brief_filter_2",
"content_format": "{\"data\":[\"instruction_1\", \"instruction_2\", ...]}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Remove the following topics from the provided list:\nSEO, natural referencing, duplication, backlinks, links, anchors, sponsorship, illustrations, images, word count, internal link, anchor, external link, original, unique, duplicated, AI, artificial intelligence, click, homepage, home, publication, linksgarden, approval, verification, category, no follow, do follow, link, guideline, guidelines, orphan, hierarchy, contextualize, copy-paste, proofread, bold, italic, bullet list, words, URL, site name, brand, name.",
"model": "gpt-4o-mini",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":[\"instruction_1\", \"instruction_2\", ...]} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Remove the following topics from the provided list: SEO, natural referencing, duplication, backlinks, links, anchors, sponsorship, illustrations, images, word count, internal link, anchor, external link, original, unique, duplicated, AI, artificial intelligence, click, homepage, home, publication, linksgarden, approval, verification, category, no follow, do follow, link, guideline, guidelines, orphan, hierarchy, contextualize, copy-paste, proofread, bold, italic, bullet list, words, URL, site name, brand, name."
},
"content": "{\"data\":[\"Right, 'Cloud Native' is all about crafting and running applications that properly leverage the cloud computing setup.\",\"Top benefits include: quicker development, improved scalability (handling loads more users with ease), boosted resilience (less time offline, yeah?), and cheaper costs all round.\",\"Key practices include: using containers (like Docker, see?), microservices (breaking apps down into smaller bits, like), DevOps (developers and operations mucking in together), and automation (doing things automatically, of course).\",\"Basically, it's about creating apps that are born in the cloud and flourish there, instead of just being bunged into it as an afterthought, innit.\"]}"
},
"response": {
"status": "ok",
"response": [
"Right, 'Cloud Native' is all about crafting and running applications that properly leverage the cloud computing setup.",
"Top benefits include quicker development, improved scalability (handling loads more users with ease), boosted resilience (less time offline, yeah?), and cheaper costs all round.",
"Key practices include using containers, microservices, DevOps, and automation.",
"Basically, it's about creating apps that are born in the cloud and flourish there, instead of just being bunged into it as an afterthought, innit."
]
}
} {
"prompt": {
"label": "generate_clusters",
"prompt": {
"prompt_id": "5",
"prompt_label": "generate_clusters",
"content_format": "{\"data\":\"keyword\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "We will give you a keyword, an idea, or a phrase. You will need to provide 20 thematic cluster ideas related to the keyword.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"keyword\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} We will give you a keyword, an idea, or a phrase. You will need to provide 20 thematic cluster ideas related to the keyword."
},
"content": "{\"data\":\"Understanding Cloud Native: Key Benefits and Practices\"}"
},
"response": {
"status": "ok",
"response": [
"Microservices Architecture: Designing and implementing cloud-native applications with independent, scalable services.",
"Containerisation with Docker: Packaging applications and their dependencies into lightweight, portable containers.",
"Orchestration with Kubernetes: Automating the deployment, scaling, and management of containerised applications.",
"CI/CD Pipelines for Cloud Native: Implementing continuous integration and continuous delivery for rapid software releases.",
"DevOps Practices in the Cloud: Fostering collaboration and automation between development and operations teams.",
"Twelve-Factor App Methodology: Building robust and scalable cloud-native applications following established principles.",
"Cloud-Native Observability: Monitoring and logging cloud-native applications for performance and troubleshooting.",
"Service Meshes: Managing service-to-service communication and security in microservices architectures.",
"API Gateways: Exposing and managing APIs for cloud-native applications.",
"Serverless Computing: Building and deploying applications without managing underlying infrastructure.",
"Cloud-Native Security: Implementing security best practices for cloud-native environments.",
"Immutable Infrastructure: Deploying applications on immutable infrastructure for increased reliability and consistency.",
"Declarative Configuration: Managing application configurations in a declarative manner for reproducibility and automation.",
"Autoscaling and Elasticity: Scaling cloud-native applications automatically based on demand.",
"Fault Tolerance and Resilience: Designing cloud-native applications to be resilient to failures.",
"Cloud-Native Data Management: Using cloud-native databases and data stores for scalable and reliable data storage.",
"Cloud-Native Networking: Configuring networking for cloud-native applications using tools like Calico or Cilium.",
"Cloud-Native Cost Optimisation: Optimising the cost of running cloud-native applications in the cloud.",
"Cloud-Native Governance and Compliance: Ensuring compliance with regulations and policies in cloud-native environments.",
"Future Trends in Cloud Native: Exploring emerging technologies and trends in the cloud-native landscape."
]
}
} {
"prompt": {
"label": "content_subtitles",
"prompt": {
"prompt_id": "11",
"prompt_label": "content_subtitles",
"content_format": "{title:title, brief:['instruction_1', 'instruction_2', etc], keywords:['keyword_1', 'keyword_2', etc], sub_number:\"Number of subtitle\"}",
"success_format": "{\"status\": \"ok\", \"response\": [{\"main_title\": \"title of the provided content\", \"sub_1\": {\"h2\": \"the first main subtitle\", \"h3_1\": \"the first subtitle 1\", \"h3_2\": \"the first subtitle 2\"}, \"sub_2\": {\"h2\": \"the second main subtitle\",\"h3_1\": \"the second subtitle 1\",\"h3_2\": \"the second subtitle 2\"}, etc...}]}\n\n\n\n\n\n",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "1",
"prompt_content": "We will give you a content title, a comment, and important keywords to use. You will need to provide a certain number of main blog article subtitles with this information, along with 2 sub-subtitles for each main subtitle.",
"model": "claude-sonnet-4-5-20250929",
"max_tokens": 4096,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {title:title, brief:['instruction_1', 'instruction_2', etc], keywords:['keyword_1', 'keyword_2', etc], sub_number:\"Number of subtitle\"} Response format in case of success: {\"status\": \"ok\", \"response\": [{\"main_title\": \"title of the provided content\", \"sub_1\": {\"h2\": \"the first main subtitle\", \"h3_1\": \"the first subtitle 1\", \"h3_2\": \"the first subtitle 2\"}, \"sub_2\": {\"h2\": \"the second main subtitle\",\"h3_1\": \"the second subtitle 1\",\"h3_2\": \"the second subtitle 2\"}, etc...}]} Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} We will give you a content title, a comment, and important keywords to use. You will need to provide a certain number of main blog article subtitles with this information, along with 2 sub-subtitles for each main subtitle.This list of words is prohibited, you must not say that these words are prohibited, you must not use them: In conclusion, However, It is important to note, Additionally, Therefore, As mentioned earlier, That being said, On the other hand, In this case, To clarify, For example, With that in mind, In summary, It is worth noting, Essentially, According to, In other words, Let me explain, In general, Ultimately"
},
"content": "{\"data\":{\"title\":\"Understanding Cloud Native: Key Benefits and Practices\",\"brief\":\"[\\\"Right, 'Cloud Native' is all about crafting and running applications that properly leverage the cloud computing setup.\\\",\\\"Top benefits include quicker development, improved scalability (handling loads more users with ease), boosted resilience (less time offline, yeah?), and cheaper costs all round.\\\",\\\"Key practices include using containers, microservices, DevOps, and automation.\\\",\\\"Basically, it's about creating apps that are born in the cloud and flourish there, instead of just being bunged into it as an afterthought, innit.\\\"]\",\"keywords\":\"\",\"sub_number\":2}}"
},
"response": {
"status": "ok",
"response": [
{
"main_title": "Understanding Cloud Native: Key Benefits and Practices",
"sub_1": {
"h2": "What Cloud Native Really Means for Modern Applications",
"h3_1": "Defining Cloud Native Architecture and Its Core Principles",
"h3_2": "How Cloud Native Differs from Traditional Application Deployment"
},
"sub_2": {
"h2": "The Business Advantages of Adopting Cloud Native Technologies",
"h3_1": "Accelerated Development Cycles and Faster Time to Market",
"h3_2": "Enhanced Scalability and Cost Efficiency in Cloud Environments"
},
"sub_3": {
"h2": "Essential Cloud Native Practices: Containers and Microservices",
"h3_1": "Leveraging Containerisation for Application Portability",
"h3_2": "Breaking Down Monoliths with Microservices Architecture"
},
"sub_4": {
"h2": "DevOps and Automation: The Foundation of Cloud Native Success",
"h3_1": "Implementing Continuous Integration and Continuous Deployment",
"h3_2": "Automating Infrastructure Management for Improved Resilience"
}
}
]
}
} {
"prompt": {
"label": "is_firewall",
"prompt": {
"prompt_id": "6",
"prompt_label": "is_firewall",
"content_format": "{\"data\":\"content\"}",
"success_format": "{\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"}",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON.\nIgnore cookie requests in your judgment.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: {\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"} Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON. Ignore cookie requests in your judgment."
},
"content": "{\"data\":\"Click to view our accessibility policy\\nSkip to content\\nAbout\\nServices\\nSolutions\\nPricing\\nPartners\\nResources\\nClose Search\\nSearch Oracle.com\\nQUICK LINKS\\nOracle Cloud Infrastructure\\nOracle Fusion Cloud Applications\\nOracle Database\\nDownload Java\\nCareers at Oracle\\nSearch\\nCountry\\nMenu\\nMenu\\nContact Us\\nSign in to Oracle Cloud\\nOracle United Kingdom\\nCloud\\nCloud Native\\nWhat Is Cloud Native? Key Features and Uses\\nAlan Zeichick | Senior Writer | October 8, 2025\\nIn This Article\\nWhat Is Cloud Native?\\nCloud Native Explained\\nKey Components of Cloud Native Development\\nVIDEO: What is Cloud Native?\\nBenefits of Adopting Cloud Native Approaches\\nChallenges of Cloud Native\\nBest Practices for Implementing Cloud Native Solutions\\nAccelerate App Development with Cloud Native Agility\\nCloud Native FAQs\\nCloud native computing is a way of designing, creating, deploying, and running applications that takes full advantage of the capabilities of a cloud platform. While traditional software\\u2014sometimes called monolithic software\\u2014can be run in either a data center or in a public cloud, such software can\\u2019t leverage the scalability and cost-efficiencies of the cloud environment.\\nThat\\u2019s where cloud native computing comes in. Instead of being crafted as a single application that\\u2019s installed onto a server, cloud native software is compiled from dozens, hundreds, or even thousands of small pieces of software. Those pieces, called microservices, are placed into containers that are installed onto cloud servers. Microservices then communicate over high-speed secure networks, working together to solve business problems.\\nWhat are the upsides of this modular approach? There are many, which we shall explore in this document. Here are four of the most significant benefits.\\nMicroservices can be written, tested, and deployed independently, accelerating the development process.\\nIf a defect is found in a particular microservice\\u2019s design or implementation, that one microservice can be debugged, improved, and replaced without affecting the rest of the application.\\nIf a microservice is overloaded because of unexpectedly high usage, that microservice\\u2019s container can be replicated with one or more identical twins, each installed on different servers, and the workload can be shared between them. This reduces or eliminates performance bottlenecks.\\nThe developers crafting a particular microservice have the flexibility to use the most appropriate tools, processor architectures, and even programming languages for the service they\\u2019re building.\\nLet\\u2019s go deeper into the concepts and introduce the terminology used to describe the specifics of cloud native computing.\\nWhat Is Cloud Native?\\nThe term \\u201ccloud native\\u201d refers to the concept of designing, building, deploying, running, and managing applications in a way that takes advantage of the distributed computing you\\u2019ll find in the cloud. Cloud native apps are architected to exploit the scale, elasticity, resiliency, and flexibility the cloud provides.\\nThe\\nCloud Native Computing Foundation (CNCF)\\n, the independent organization that manages many of the open standards that make cloud native work, defines the concept this way.\\nCloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach.\\nThese techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil.\\nIt\\u2019s worth taking time to unpack that definition.\\nScalable applications are those that can handle increased workloads without a need to rewrite or redesign the software. The dynamic environments in the definition are cloud computing platforms, such as Oracle Cloud Infrastructure (OCI), but also other public, private, and hybrid clouds from all the major service providers.\\nThe technologies in that definition are the containers that hold individual microservices and the service mesh infrastructure that ties those containers together via high-speed networks that support security, observability, policy enforcement, and service discovery. Immutable infrastructure means that once deployed, containers are never modified; instead, they\\u2019re replaced in a carefully controlled manner. This allows a distributed application to be both predictable and replicable\\u2014that is, all copies of a container or a microservice will be exactly the same.\\nA final and very important concept is \\u201cloosely coupled.\\u201d That means that when microservices are working with other microservices, they know how to communicate by well-defined protocols, called declarative APIs, which painstakingly describe what the microservice does, what data the microservice requires, and what data the microservice returns after it completes its work. These inner workings of that microservice are hidden and can be changed at any time without affecting any other part of the application, making the whole application resilient, scalable, and easier to update.\\nCloud native applications can be run in any cloud architecture: public, private, hybrid, or multicloud. A public cloud is one where data is transmitted between the cloud application and the end user or a corporate data center via the internet. A private cloud is one where the data is transmitted entirely within secure networks, such as a cloud service set up within a data center. A\\nhybrid cloud\\nuses a combination of public clouds, private clouds, and corporate data centers. Additionally, a\\nmulticloud deployment\\nspans more than one commercial cloud provider; part of the application might be OCI, and another part might be running in Microsoft Azure, for example.\\nCloud native applications leverage microservices running inside containers that are installed onto cloud servers. DevOps teams, combining the traditional functions of software developers and systems administrators, use continuous integration (CI) to create and enhance microservices and continuous delivery (CD) to push those new microservices out to the cloud without affecting the rest of the application.\\nKey Takeaways\\nIn cloud native, large applications are broken down into modular pieces called microservices.\\nMicroservices may then be packaged into containers, which can be readily installed onto servers provided by a cloud vendor.\\nOrchestration software, such as Kubernetes, automates the deployment and management of containerized microservices.\\nMicroservices are designed, coded, tested, deployed, and managed independently, which means they are faster to build and can be debugged and improved without affecting the rest of the application.\\nBecause cloud native applications can better utilize a commercial cloud service, applications run more efficiently without wasting resources, and this reduces the operating cost of the software.\\nCloud Native Explained\\nCloud native applications are designed as independent microservices, packaged in lightweight, self-contained containers. These containers are highly portable and can be rapidly scaled up or down based on demand. By encapsulating microservices within containers, cloud native allows for seamless deployment across a wide range of operating environments, including data centers and commercial cloud services, and running on different types of servers, such as\\nLinux\\nor Windows.\\nIn the most common cloud native designs, an application is architected to split its functionality across dozens, hundreds, or even thousands of microservices, each designed to do a specific job. Once written, each microservice is installed into a container image, that is, a delivery vehicle that can be loaded onto a service and then executed. The most common standard for containers is\\nDocker\\n, an open source format from the CNCF that\\u2019s supported by nearly every cloud provider.\\nA completed enterprise application may have thousands of Docker containers. How do you deploy all those containers onto a cloud service, wire them up with the appropriate security and high-speed networks, ensure that messages from one microservice get routed to the correct recipients, and handle scalability and the occasional service failure? That\\u2019s where the open source\\nKubernetes platform\\ncomes in. Like Docker, Kubernetes is supported by the CNCF and has become the industry standard. Without going into all the details, suffice it to say that Kubernetes handles and automates all the complex plumbing required to run, manage, and scale a large cloud native application.\\nWith microservices inside Docker containers, and Docker containers deployed by\\nKubernetes\\nonto cloud services, you have a complete, scalable, and resilient cloud native application.\\nTraditional vs. Cloud Native Applications\\nThe opposite of a cloud native application could be termed a traditional or monolithic application that\\u2019s designed as a single codebase, typically by a single development team. The software is written and tested by that team, then handed to an operations team to deploy onto a server. If the software has a defect, the development team finds the problem, revises the software, and gives a new version to the operations team. The ops team then stops the original software, installs the replacement, and restarts. The same process is followed for adding new features\\u2014the entire application must be replaced and reinstalled.\\nBy contrast, a cloud native application is written as a collection of many microservices, each of which is a separate piece of software. Those pieces of software are designed, coded, tested, and deployed independently, without affecting the rest of the application, which makes the revision process faster and the updates smoother. Developers can choose the best tools, including programming languages, for the specific microservice they\\u2019re building.\\nTo use an analogy: Imagine if in your home, the faucet in the guest bathroom started leaking. To fix it, you needed to move out of your House 4.1, replace it with House 4.2 that doesn\\u2019t have a leaky faucet, and then move back in. Want to replace a single sink with a double sink? Move out and install House 4.3. That\\u2019s the monolithic or traditional software model. Would you do that? Of course not. A plumber would replace the faucet or a contractor could remodel the guest bathroom without affecting anything else in the house. That\\u2019s the cloud native model.\\nKey Components of Cloud Native Development\\nThe introduction of cloud native computing has also introduced a number of new concepts and terminologies that are important for understanding the benefits of the model. They include the following:\\nContainers and containerization\\nKubernetes is designed for high availability (HA). Its automatic features for healing malfunctioning Containers are the backbone of cloud native. These lightweight, self-contained packages, often created with\\nDocker\\n, include all the necessary dependencies for consistent application execution across different computing environments. Containerization enables application portability and facilitates rapid deployment.\\nContainers provide a standardized, isolated environment, allowing applications to run independently and reducing the risk of conflicts between dependencies. This isolation enhances security by confining potential vulnerabilities to individual containers. The lightweight nature of containers also contributes to efficient resource utilization.\\nMicroservices architecture\\nMicroservices\\ninvolves breaking complex applications down into smaller, independent services. Each service focuses on a specific function, enabling faster development through parallel work on different services.\\nThe\\nmicroservices architecture\\npromotes agility and flexibility. Each microservice can be developed, deployed, and scaled independently, allowing for rapid updates and new feature releases. This modularity also improves fault isolation, so that issues in one service do not affect the entire application.\\nImmutable infrastructure\\nImmutable infrastructure is a principle where deployed resources are never directly modified. Changes are implemented by creating new instances with updated configurations, offering consistency and simplifying rollback procedures.\\nInfrastructure-as-code (IaC)\\ntools automate infrastructure provisioning, enhancing efficiency and repeatability.\\nIaC allows infrastructure to be defined as code for better version control, automated testing, and consistent deployment across environments. This approach treats infrastructure as a vital application component, subject to the same rigorous management and control as the codebase.\\nAutomation and orchestration\\nAutomation is a critical aspect of cloud native, aiming to allow for large-scale deployments that would be difficult to manage manually. Container orchestration tools, such as Kubernetes, automate the management and deployment of containerized applications. These tools provide high availability, efficient resource allocation, and simplified scaling, making complex distributed systems more manageable.\\nAutomation and orchestration are essential for achieving the scalability, fault tolerance, and self-healing capabilities that define cloud native systems. Kubernetes cloud services enable dynamic resource allocation, so that applications can scale based on demand and facilitate automated recovery from failures.\\nObservability and monitoring\\nCloud native applications are designed with observability in mind; that means developers can better understand their systems\\u2019 internal workings. This involves collecting and analyzing metrics, logs, and traces to gain insights into performance, resource usage, and potential issues.\\nAdvanced monitoring tools\\nprovide real-time visibility into application health and performance. These tools enable proactive problem-solving, helping developers identify and resolve issues before they impact users. Observability and management services are crucial for optimizing application performance and resource allocation.\\nResilience and self-healing\\nResilience\\nis a key characteristic of cloud native systems that helps them recover from failures and maintain stability. Strategies such as replication, load balancing, and automated recovery mechanisms achieve this. Self-healing capabilities, as they\\u2019re called, detect and rectify issues without manual intervention, maintaining high availability.\\nCloud native applications are designed to handle failures gracefully, delivering minimal downtime. Self-healing mechanisms automatically detect and resolve issues, keeping applications running smoothly. This resilience is crucial for critical business operations and enables a reliable user experience.\\nVIDEO: What is Cloud Native?\\nBenefits of Adopting Cloud Native Approaches\\nThe cloud native approach offers organizations the potential to see significant benefits over running traditional monolithic applications. Those benefits include the following:\\nScalability and flexibility.\\nCloud native applications offer\\ndynamic scalability\\nto meet demand. Containers and microservices enable granular scaling for efficient resource utilization and cost-effectiveness. This flexibility allows businesses to quickly adapt to market changes.\\nAgile development and faster time to market.\\nThe cloud native approach accelerates development cycles. A microservices architecture enables parallel development, allowing teams to work on different services simultaneously. This results in faster releases, which can give your business a competitive edge.\\nCost efficiency.\\nCloud native architecture optimizes resource utilization, which can lead to significant\\ncost savings\\n. Organizations pay only for the resources they use, and automated processes reduce\\noperational costs\\nby minimizing manual effort.\\nEnhanced reliability and high availability.\\nCloud native systems are designed for resilience to deliver high availability. Redundancy, load balancing, and self-healing mechanisms keep applications available even during failures. This is vital for critical business operations, and software updates can be deployed with minimal downtime.\\nDevOps and CI\\/CD.\\nCloud native seamlessly aligns with\\nDevOps\\npractices, enabling efficient continuous integration and continuous delivery (CI\\/CD) pipelines. Automation streamlines the development lifecycle, promoting collaboration and efficiency.\\nStandards-based portability.\\nCloud native services often rely on open source and standards-based technology for interoperability and workload portability. This can reduce vendor lock-in and enable global infrastructure utilization, which may lead to lower latency and higher performance for users worldwide.\\nSecure by design.\\nCloud native incorporates\\nsecurity\\nat every layer. Containers provide isolated environments, helping reduce the risk of vulnerabilities. Automated security updates and policy enforcement further strengthen security posture, making\\ncloud computing\\nsuitable for even the\\nmost security-focused use cases\\n.\\nHere are some of the key features and benefits of cloud native computing.\\nFeatures\\nBenefits\\nMicroservices architecture\\nWhen enterprise applications are written as small pieces of code, each performing a different business function\\u2014called microservices\\u2014the application becomes faster to build, easier to manage, more scalable, more resilient, and far easier to upgrade and enhance.\\nContainers and containerization\\nMicroservices are often packed up into containers, and those containers can be easily deployed onto cloud servers. Because a container is carefully constructed and defined, it can run on any compatible server on a cloud service. You can even deploy many copies of a container if needed to handle a heavy workload and simply swap out an old container with an upgraded version without affecting the rest of the application.\\nContinuous integration and continuous delivery (CI\\/CD)\\nCI\\/CD is a process where development teams use a pipeline approach to design, build, test, and deploy microservices into containers, and then those containers are deployed onto cloud servers. CI\\/CD results in faster release cycles, enhances developer productivity, and lends itself to automated workflows to get software deployed faster.\\nImmutable infrastructure\\nImmutable components, such as containers, are never modified after deployment. When there\\u2019s a revision, the container is replaced. The benefits are consistency of the software, simplified rollouts, and the ability to easily replicate an application into a new cloud data center or even a new service provider.\\nDevOps practices\\nDevOps refers to merging traditional developer and operations teams into a single unit. DevOps teams write the software, test the software, and then deploy the software and manage it post-deployment. When combined with CI\\/CD and automation, new software is deployed quickly, and because there\\u2019s no finger-pointing, problems can be solved fast.\\nObservability and monitoring\\nObservability helps DevOps teams understand what\\u2019s happening inside an application while it is running. Monitoring refers to the practice of looking at log files and studying performance metrics. Together, these help teams detect and fix problems faster, tune performance, and meet service-level requirements to deliver the promised application availability and responsiveness.\\nCloud platforms\\nCloud platforms, such as OCI, generally provide everything needed to run cloud native applications, including servers capable of hosting Docker containers, secure high-speed networks, preinstalled Kubernetes engines, and tools to facilitate observability and monitoring. The scalability of cloud native applications helps improve efficiency and reduce the operating costs of cloud native software.\\nChallenges of Cloud Native\\nCloud native computing may sound complicated. That\\u2019s because it is, especially for organizations new to the cloud that have spent years\\u2014or decades\\u2014building traditional monolithic software environments. Here are some of the challenges that organizations face when leaning into cloud native computing for the first time.\\nComplexity, skills gaps, and learning curve.\\nCloud native architectures can be complex, especially for larger applications. Microservices introduce additional layers of abstraction, requiring careful design and management. Consider investing in\\ntraining and upskilling\\nyour employees to effectively work with these technologies.\\nCultural shift.\\nEmbracing cloud native often requires a cultural transformation. DevOps practices, cross-functional collaboration, and a\\nshift toward automation\\nand agility are essential. This may involve changing longstanding processes and organizational structures, requiring buy-in from all stakeholders, both technical and line of business.\\nSecurity and compliance.\\nWhile cloud native can enhance security, it introduces new considerations. Organizations must maintain secure communication between microservices, for example, which will require establishing and enforcing security controls and adherence to\\ncompliance\\nregulations.\\nManaging distributed systems.\\nCloud architectures and the requirements for using Kubernetes may be very different from your engineering team\\u2019s normal operations.\\nCost management.\\nThe flexibility of cloud native can lead to cost spikes if not properly managed. Organizations can implement monitoring strategies and leverage\\ncloud provider tools\\nfor cost optimization.\\nBest Practices for Implementing Cloud Native Solutions\\nNo two organizations will follow the same pathway to cloud native computing. What you will find, however, is that most keep these seven best practices in mind.\\nAdopt a microservices architecture.\\nYour architects will break applications down into independent microservices, each focused on a specific business function. Then, your developers\\u2014or ideally, DevOps team\\u2014can build, test, deploy, and scale those microservices independently, increasing agility and resilience.\\nStandardize on containers.\\nUsing containers\\u2014generally Docker\\u2014to package microservices into easy-to-deploy and easy-to-manage units helps ensure reliability from development through production, especially if you\\u2019re using a CI\\/CD pipeline.\\nAutomate deployment and scaling.\\nYour DevOps teams can use CI\\/CD to automate software builds, tests, and deployments for rapid and reliable software delivery. What\\u2019s more, if you use a\\nplatform like Kubernetes\\n, your pipeline can handle automatic scaling and reduce the likelihood of human error.\\nUse\\ninfrastructure as code (IaC)\\nand immutable infrastructure.\\nAdvanced IaC and immutability toolchains can work with Kubernetes to automate the creation of secure high-speed networks and help ensure that your application can be quickly installed where you need it.\\nPrioritize observability and monitoring.\\nIf you can\\u2019t see it, you can\\u2019t manage it. So emphasize that microservices be designed to generate robust logs and support common observability and monitoring standards.\\nIntegrate security at every layer.\\nBaking security into every phase of the application design and deployment process is critical. Many organizations are opting to adopt a\\nzero trust approach\\n.\\nOptimize costs and resource utilization.\\nCloud computing is an OpEx (operational expense) business resource: the more you use, the higher the bill. So unlike with traditional applications in a data center, there\\u2019s an immediate payoff to improving efficiency and rightsizing resources to match workloads.\\nAccelerate App Development with Cloud Native Agility\\nOracle provides everything needed to build and deploy cloud native applications, including tooling, services, and automation, so that development teams can build quickly while reducing the number of operational tasks.\\nOracle cloud native services\\nrun on OCI, which offers a standards-based platform with higher performance and lower cost compared to other cloud providers. By taking advantage of services based on open source and open standards, OCI makes it possible for developers to run applications on any cloud or on-premises environment without refactoring. This flexibility provides the freedom to focus on building and innovating, such as with the help of powerful generative AI and even prebuilt AI\\/ML services, to breathe new capabilities and intelligence into your existing applications.\\nDoes cloud native application development truly deliver apps that are much better than traditionally developed apps? Yes. The benefits are clear: Cloud native apps can scale because their functions are broken into microservices, and they allow for individual management. What\\u2019s more, cloud native apps can run in a highly distributed manner, maintaining independence and allocating resources based on application needs.\\nCloud native applications can help strengthen business strategy and value because they can provide a consistent experience across private, public, and hybrid clouds. They allow your organization to take full advantage of cloud computing by running responsive and reliable scalable applications.\\nLooking to dig deeper into cloud native architectures? Download our free ebook to discover Any organization can adopt cloud native development strategies now.\\nAccess the ebook\\nCloud Native FAQs\\nHow does cloud native architecture differ from traditional application architectures?\\nCloud native architecture breaks large, complex business applications into many microservices, each of which performs a business function. The application works when these microservices communicate with one another over a high-speed network to collaborate on a task. Each microservice is defined, designed, built, tested, deployed, managed, and upgraded separately, which can result in faster deployments and much greater scalability. For example, when a microservice sees a high workload, a cloud native application can automatically make a copy of that microservice on a different server and split the workload between them. By contrast, a traditional application architecture consists of a single software code base\\u2014a monolith\\u2014that is designed, built, tested, and deployed as one unit. Bug fixes or upgrades result in changes to the monolith, which must then be redeployed. Because of this, software rollouts are often slow. Scalability is a challenge and often requires either rearchitecting (and rewriting) the software, or installing it on a faster, more expensive server.\\nHow can businesses effectively transition their existing applications to become cloud native?\\nExisting monolithic applications can be rearchitected into cloud native applications. The process is to identify parts of the code that can be split off into microservices, often beginning with the sections of code that are easiest to separate or are causing performance bottlenecks. By handling these sections one at a time, a monolithic application can realize many of the benefits of the cloud native approach.\\nWhat is the CNCF?\\nThe Cloud Native Computing Foundation (CNCF) is a vendor neutral open source organization hosted by the Linux Foundation. The CNCF\\u2019s goal is to promote cloud native technologies, and it provides essential support for many project and industry standards, such as the Docker container format and the Kubernetes container automation and orchestration platform. Many cloud services providers, including Oracle, contribute to the CNCF\\u2019s work and have adopted its standards to promote interoperability between cloud ecosystems.\\nWhat is the difference between cloud and cloud native?\\nCloud refers to computing services that are hosted by commercial service providers, such as Oracle. Those computing services include servers of many types, high-speed networks, storage systems, libraries of advanced computing functions (such as for AI and security), and even business applications. Nearly every website or application you access through a web browser is wholly or partially in the cloud; the rest reside in corporate data centers. Many mobile phone apps, too, rely on the cloud to provide essential functionality.\\nCloud native is an approach to building business applications that breaks up that application into dozens or hundreds of microservices. Each microservice encapsulates a key piece of business functionality. The application comes together to solve business problems when those microservices collaborate with each other over secure high-speed networks, with each microservice performing its own piece of the workload. Cloud native applications leverage a cloud services provider\\u2019s resources to make the application scalable, efficient, and resilient.\\nResources for\\nCareers\\nDevelopers\\nInvestors\\nPartners\\nStartups\\nStudents and Educators\\nWhy Oracle\\nAnalyst Reports\\nOCI | Microsoft Azure\\nCloud Reference Architectures\\nCorporate Responsibility\\nCulture and Inclusion\\nSecurity Practices\\nLearn\\nWhat is AI?\\nWhat is cloud computing?\\nWhat is Cloud Storage?\\nWhat is HPC?\\nWhat is IaaS?\\nWhat is PaaS?\\nWhat\\u2019s New\\nOracle Cloud Free Tier\\nCloud Architecture Center\\nCloud Lift\\nOracle Support Rewards\\nOracle Red Bull Racing\\nContact Us\\nSales: +44 207 5626 823\\nHow can we help?\\nSubscribe to emails\\nEvents\\nNews\\nOCI Blog\\nCountry\\/Region\\n\\u00a9 2026 Oracle\\nTerms of Use and Privacy\\nGender Pay Gap Report\\nModern Slavery Statement\\nAd Choices\\nCareers\\n\"}"
},
"response": {
"status": "ok",
"response": "false"
}
} {
"prompt": {
"label": "resume_data",
"prompt": {
"prompt_id": "7",
"prompt_label": "resume_data",
"content_format": "{\"data\":\"content\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you."
},
"content": "{\"data\":\"Click to view our accessibility policy\\nSkip to content\\nAbout\\nServices\\nSolutions\\nPricing\\nPartners\\nResources\\nClose Search\\nSearch Oracle.com\\nQUICK LINKS\\nOracle Cloud Infrastructure\\nOracle Fusion Cloud Applications\\nOracle Database\\nDownload Java\\nCareers at Oracle\\nSearch\\nCountry\\nMenu\\nMenu\\nContact Us\\nSign in to Oracle Cloud\\nOracle United Kingdom\\nCloud\\nCloud Native\\nWhat Is Cloud Native? Key Features and Uses\\nAlan Zeichick | Senior Writer | October 8, 2025\\nIn This Article\\nWhat Is Cloud Native?\\nCloud Native Explained\\nKey Components of Cloud Native Development\\nVIDEO: What is Cloud Native?\\nBenefits of Adopting Cloud Native Approaches\\nChallenges of Cloud Native\\nBest Practices for Implementing Cloud Native Solutions\\nAccelerate App Development with Cloud Native Agility\\nCloud Native FAQs\\nCloud native computing is a way of designing, creating, deploying, and running applications that takes full advantage of the capabilities of a cloud platform. While traditional software\\u2014sometimes called monolithic software\\u2014can be run in either a data center or in a public cloud, such software can\\u2019t leverage the scalability and cost-efficiencies of the cloud environment.\\nThat\\u2019s where cloud native computing comes in. Instead of being crafted as a single application that\\u2019s installed onto a server, cloud native software is compiled from dozens, hundreds, or even thousands of small pieces of software. Those pieces, called microservices, are placed into containers that are installed onto cloud servers. Microservices then communicate over high-speed secure networks, working together to solve business problems.\\nWhat are the upsides of this modular approach? There are many, which we shall explore in this document. Here are four of the most significant benefits.\\nMicroservices can be written, tested, and deployed independently, accelerating the development process.\\nIf a defect is found in a particular microservice\\u2019s design or implementation, that one microservice can be debugged, improved, and replaced without affecting the rest of the application.\\nIf a microservice is overloaded because of unexpectedly high usage, that microservice\\u2019s container can be replicated with one or more identical twins, each installed on different servers, and the workload can be shared between them. This reduces or eliminates performance bottlenecks.\\nThe developers crafting a particular microservice have the flexibility to use the most appropriate tools, processor architectures, and even programming languages for the service they\\u2019re building.\\nLet\\u2019s go deeper into the concepts and introduce the terminology used to describe the specifics of cloud native computing.\\nWhat Is Cloud Native?\\nThe term \\u201ccloud native\\u201d refers to the concept of designing, building, deploying, running, and managing applications in a way that takes advantage of the distributed computing you\\u2019ll find in the cloud. Cloud native apps are architected to exploit the scale, elasticity, resiliency, and flexibility the cloud provides.\\nThe\\nCloud Native Computing Foundation (CNCF)\\n, the independent organization that manages many of the open standards that make cloud native work, defines the concept this way.\\nCloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach.\\nThese techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil.\\nIt\\u2019s worth taking time to unpack that definition.\\nScalable applications are those that can handle increased workloads without a need to rewrite or redesign the software. The dynamic environments in the definition are cloud computing platforms, such as Oracle Cloud Infrastructure (OCI), but also other public, private, and hybrid clouds from all the major service providers.\\nThe technologies in that definition are the containers that hold individual microservices and the service mesh infrastructure that ties those containers together via high-speed networks that support security, observability, policy enforcement, and service discovery. Immutable infrastructure means that once deployed, containers are never modified; instead, they\\u2019re replaced in a carefully controlled manner. This allows a distributed application to be both predictable and replicable\\u2014that is, all copies of a container or a microservice will be exactly the same.\\nA final and very important concept is \\u201cloosely coupled.\\u201d That means that when microservices are working with other microservices, they know how to communicate by well-defined protocols, called declarative APIs, which painstakingly describe what the microservice does, what data the microservice requires, and what data the microservice returns after it completes its work. These inner workings of that microservice are hidden and can be changed at any time without affecting any other part of the application, making the whole application resilient, scalable, and easier to update.\\nCloud native applications can be run in any cloud architecture: public, private, hybrid, or multicloud. A public cloud is one where data is transmitted between the cloud application and the end user or a corporate data center via the internet. A private cloud is one where the data is transmitted entirely within secure networks, such as a cloud service set up within a data center. A\\nhybrid cloud\\nuses a combination of public clouds, private clouds, and corporate data centers. Additionally, a\\nmulticloud deployment\\nspans more than one commercial cloud provider; part of the application might be OCI, and another part might be running in Microsoft Azure, for example.\\nCloud native applications leverage microservices running inside containers that are installed onto cloud servers. DevOps teams, combining the traditional functions of software developers and systems administrators, use continuous integration (CI) to create and enhance microservices and continuous delivery (CD) to push those new microservices out to the cloud without affecting the rest of the application.\\nKey Takeaways\\nIn cloud native, large applications are broken down into modular pieces called microservices.\\nMicroservices may then be packaged into containers, which can be readily installed onto servers provided by a cloud vendor.\\nOrchestration software, such as Kubernetes, automates the deployment and management of containerized microservices.\\nMicroservices are designed, coded, tested, deployed, and managed independently, which means they are faster to build and can be debugged and improved without affecting the rest of the application.\\nBecause cloud native applications can better utilize a commercial cloud service, applications run more efficiently without wasting resources, and this reduces the operating cost of the software.\\nCloud Native Explained\\nCloud native applications are designed as independent microservices, packaged in lightweight, self-contained containers. These containers are highly portable and can be rapidly scaled up or down based on demand. By encapsulating microservices within containers, cloud native allows for seamless deployment across a wide range of operating environments, including data centers and commercial cloud services, and running on different types of servers, such as\\nLinux\\nor Windows.\\nIn the most common cloud native designs, an application is architected to split its functionality across dozens, hundreds, or even thousands of microservices, each designed to do a specific job. Once written, each microservice is installed into a container image, that is, a delivery vehicle that can be loaded onto a service and then executed. The most common standard for containers is\\nDocker\\n, an open source format from the CNCF that\\u2019s supported by nearly every cloud provider.\\nA completed enterprise application may have thousands of Docker containers. How do you deploy all those containers onto a cloud service, wire them up with the appropriate security and high-speed networks, ensure that messages from one microservice get routed to the correct recipients, and handle scalability and the occasional service failure? That\\u2019s where the open source\\nKubernetes platform\\ncomes in. Like Docker, Kubernetes is supported by the CNCF and has become the industry standard. Without going into all the details, suffice it to say that Kubernetes handles and automates all the complex plumbing required to run, manage, and scale a large cloud native application.\\nWith microservices inside Docker containers, and Docker containers deployed by\\nKubernetes\\nonto cloud services, you have a complete, scalable, and resilient cloud native application.\\nTraditional vs. Cloud Native Applications\\nThe opposite of a cloud native application could be termed a traditional or monolithic application that\\u2019s designed as a single codebase, typically by a single development team. The software is written and tested by that team, then handed to an operations team to deploy onto a server. If the software has a defect, the development team finds the problem, revises the software, and gives a new version to the operations team. The ops team then stops the original software, installs the replacement, and restarts. The same process is followed for adding new features\\u2014the entire application must be replaced and reinstalled.\\nBy contrast, a cloud native application is written as a collection of many microservices, each of which is a separate piece of software. Those pieces of software are designed, coded, tested, and deployed independently, without affecting the rest of the application, which makes the revision process faster and the updates smoother. Developers can choose the best tools, including programming languages, for the specific microservice they\\u2019re building.\\nTo use an analogy: Imagine if in your home, the faucet in the guest bathroom started leaking. To fix it, you needed to move out of your House 4.1, replace it with House 4.2 that doesn\\u2019t have a leaky faucet, and then move back in. Want to replace a single sink with a double sink? Move out and install House 4.3. That\\u2019s the monolithic or traditional software model. Would you do that? Of course not. A plumber would replace the faucet or a contractor could remodel the guest bathroom without affecting anything else in the house. That\\u2019s the cloud native model.\\nKey Components of Cloud Native Development\\nThe introduction of cloud native computing has also introduced a number of new concepts and terminologies that are important for understanding the benefits of the model. They include the following:\\nContainers and containerization\\nKubernetes is designed for high availability (HA). Its automatic features for healing malfunctioning Containers are the backbone of cloud native. These lightweight, self-contained packages, often created with\\nDocker\\n, include all the necessary dependencies for consistent application execution across different computing environments. Containerization enables application portability and facilitates rapid deployment.\\nContainers provide a standardized, isolated environment, allowing applications to run independently and reducing the risk of conflicts between dependencies. This isolation enhances security by confining potential vulnerabilities to individual containers. The lightweight nature of containers also contributes to efficient resource utilization.\\nMicroservices architecture\\nMicroservices\\ninvolves breaking complex applications down into smaller, independent services. Each service focuses on a specific function, enabling faster development through parallel work on different services.\\nThe\\nmicroservices architecture\\npromotes agility and flexibility. Each microservice can be developed, deployed, and scaled independently, allowing for rapid updates and new feature releases. This modularity also improves fault isolation, so that issues in one service do not affect the entire application.\\nImmutable infrastructure\\nImmutable infrastructure is a principle where deployed resources are never directly modified. Changes are implemented by creating new instances with updated configurations, offering consistency and simplifying rollback procedures.\\nInfrastructure-as-code (IaC)\\ntools automate infrastructure provisioning, enhancing efficiency and repeatability.\\nIaC allows infrastructure to be defined as code for better version control, automated testing, and consistent deployment across environments. This approach treats infrastructure as a vital application component, subject to the same rigorous management and control as the codebase.\\nAutomation and orchestration\\nAutomation is a critical aspect of cloud native, aiming to allow for large-scale deployments that would be difficult to manage manually. Container orchestration tools, such as Kubernetes, automate the management and deployment of containerized applications. These tools provide high availability, efficient resource allocation, and simplified scaling, making complex distributed systems more manageable.\\nAutomation and orchestration are essential for achieving the scalability, fault tolerance, and self-healing capabilities that define cloud native systems. Kubernetes cloud services enable dynamic resource allocation, so that applications can scale based on demand and facilitate automated recovery from failures.\\nObservability and monitoring\\nCloud native applications are designed with observability in mind; that means developers can better understand their systems\\u2019 internal workings. This involves collecting and analyzing metrics, logs, and traces to gain insights into performance, resource usage, and potential issues.\\nAdvanced monitoring tools\\nprovide real-time visibility into application health and performance. These tools enable proactive problem-solving, helping developers identify and resolve issues before they impact users. Observability and management services are crucial for optimizing application performance and resource allocation.\\nResilience and self-healing\\nResilience\\nis a key characteristic of cloud native systems that helps them recover from failures and maintain stability. Strategies such as replication, load balancing, and automated recovery mechanisms achieve this. Self-healing capabilities, as they\\u2019re called, detect and rectify issues without manual intervention, maintaining high availability.\\nCloud native applications are designed to handle failures gracefully, delivering minimal downtime. Self-healing mechanisms automatically detect and resolve issues, keeping applications running smoothly. This resilience is crucial for critical business operations and enables a reliable user experience.\\nVIDEO: What is Cloud Native?\\nBenefits of Adopting Cloud Native Approaches\\nThe cloud native approach offers organizations the potential to see significant benefits over running traditional monolithic applications. Those benefits include the following:\\nScalability and flexibility.\\nCloud native applications offer\\ndynamic scalability\\nto meet demand. Containers and microservices enable granular scaling for efficient resource utilization and cost-effectiveness. This flexibility allows businesses to quickly adapt to market changes.\\nAgile development and faster time to market.\\nThe cloud native approach accelerates development cycles. A microservices architecture enables parallel development, allowing teams to work on different services simultaneously. This results in faster releases, which can give your business a competitive edge.\\nCost efficiency.\\nCloud native architecture optimizes resource utilization, which can lead to significant\\ncost savings\\n. Organizations pay only for the resources they use, and automated processes reduce\\noperational costs\\nby minimizing manual effort.\\nEnhanced reliability and high availability.\\nCloud native systems are designed for resilience to deliver high availability. Redundancy, load balancing, and self-healing mechanisms keep applications available even during failures. This is vital for critical business operations, and software updates can be deployed with minimal downtime.\\nDevOps and CI\\/CD.\\nCloud native seamlessly aligns with\\nDevOps\\npractices, enabling efficient continuous integration and continuous delivery (CI\\/CD) pipelines. Automation streamlines the development lifecycle, promoting collaboration and efficiency.\\nStandards-based portability.\\nCloud native services often rely on open source and standards-based technology for interoperability and workload portability. This can reduce vendor lock-in and enable global infrastructure utilization, which may lead to lower latency and higher performance for users worldwide.\\nSecure by design.\\nCloud native incorporates\\nsecurity\\nat every layer. Containers provide isolated environments, helping reduce the risk of vulnerabilities. Automated security updates and policy enforcement further strengthen security posture, making\\ncloud computing\\nsuitable for even the\\nmost security-focused use cases\\n.\\nHere are some of the key features and benefits of cloud native computing.\\nFeatures\\nBenefits\\nMicroservices architecture\\nWhen enterprise applications are written as small pieces of code, each performing a different business function\\u2014called microservices\\u2014the application becomes faster to build, easier to manage, more scalable, more resilient, and far easier to upgrade and enhance.\\nContainers and containerization\\nMicroservices are often packed up into containers, and those containers can be easily deployed onto cloud servers. Because a container is carefully constructed and defined, it can run on any compatible server on a cloud service. You can even deploy many copies of a container if needed to handle a heavy workload and simply swap out an old container with an upgraded version without affecting the rest of the application.\\nContinuous integration and continuous delivery (CI\\/CD)\\nCI\\/CD is a process where development teams use a pipeline approach to design, build, test, and deploy microservices into containers, and then those containers are deployed onto cloud servers. CI\\/CD results in faster release cycles, enhances developer productivity, and lends itself to automated workflows to get software deployed faster.\\nImmutable infrastructure\\nImmutable components, such as containers, are never modified after deployment. When there\\u2019s a revision, the container is replaced. The benefits are consistency of the software, simplified rollouts, and the ability to easily replicate an application into a new cloud data center or even a new service provider.\\nDevOps practices\\nDevOps refers to merging traditional developer and operations teams into a single unit. DevOps teams write the software, test the software, and then deploy the software and manage it post-deployment. When combined with CI\\/CD and automation, new software is deployed quickly, and because there\\u2019s no finger-pointing, problems can be solved fast.\\nObservability and monitoring\\nObservability helps DevOps teams understand what\\u2019s happening inside an application while it is running. Monitoring refers to the practice of looking at log files and studying performance metrics. Together, these help teams detect and fix problems faster, tune performance, and meet service-level requirements to deliver the promised application availability and responsiveness.\\nCloud platforms\\nCloud platforms, such as OCI, generally provide everything needed to run cloud native applications, including servers capable of hosting Docker containers, secure high-speed networks, preinstalled Kubernetes engines, and tools to facilitate observability and monitoring. The scalability of cloud native applications helps improve efficiency and reduce the operating costs of cloud native software.\\nChallenges of Cloud Native\\nCloud native computing may sound complicated. That\\u2019s because it is, especially for organizations new to the cloud that have spent years\\u2014or decades\\u2014building traditional monolithic software environments. Here are some of the challenges that organizations face when leaning into cloud native computing for the first time.\\nComplexity, skills gaps, and learning curve.\\nCloud native architectures can be complex, especially for larger applications. Microservices introduce additional layers of abstraction, requiring careful design and management. Consider investing in\\ntraining and upskilling\\nyour employees to effectively work with these technologies.\\nCultural shift.\\nEmbracing cloud native often requires a cultural transformation. DevOps practices, cross-functional collaboration, and a\\nshift toward automation\\nand agility are essential. This may involve changing longstanding processes and organizational structures, requiring buy-in from all stakeholders, both technical and line of business.\\nSecurity and compliance.\\nWhile cloud native can enhance security, it introduces new considerations. Organizations must maintain secure communication between microservices, for example, which will require establishing and enforcing security controls and adherence to\\ncompliance\\nregulations.\\nManaging distributed systems.\\nCloud architectures and the requirements for using Kubernetes may be very different from your engineering team\\u2019s normal operations.\\nCost management.\\nThe flexibility of cloud native can lead to cost spikes if not properly managed. Organizations can implement monitoring strategies and leverage\\ncloud provider tools\\nfor cost optimization.\\nBest Practices for Implementing Cloud Native Solutions\\nNo two organizations will follow the same pathway to cloud native computing. What you will find, however, is that most keep these seven best practices in mind.\\nAdopt a microservices architecture.\\nYour architects will break applications down into independent microservices, each focused on a specific business function. Then, your developers\\u2014or ideally, DevOps team\\u2014can build, test, deploy, and scale those microservices independently, increasing agility and resilience.\\nStandardize on containers.\\nUsing containers\\u2014generally Docker\\u2014to package microservices into easy-to-deploy and easy-to-manage units helps ensure reliability from development through production, especially if you\\u2019re using a CI\\/CD pipeline.\\nAutomate deployment and scaling.\\nYour DevOps teams can use CI\\/CD to automate software builds, tests, and deployments for rapid and reliable software delivery. What\\u2019s more, if you use a\\nplatform like Kubernetes\\n, your pipeline can handle automatic scaling and reduce the likelihood of human error.\\nUse\\ninfrastructure as code (IaC)\\nand immutable infrastructure.\\nAdvanced IaC and immutability toolchains can work with Kubernetes to automate the creation of secure high-speed networks and help ensure that your application can be quickly installed where you need it.\\nPrioritize observability and monitoring.\\nIf you can\\u2019t see it, you can\\u2019t manage it. So emphasize that microservices be designed to generate robust logs and support common observability and monitoring standards.\\nIntegrate security at every layer.\\nBaking security into every phase of the application design and deployment process is critical. Many organizations are opting to adopt a\\nzero trust approach\\n.\\nOptimize costs and resource utilization.\\nCloud computing is an OpEx (operational expense) business resource: the more you use, the higher the bill. So unlike with traditional applications in a data center, there\\u2019s an immediate payoff to improving efficiency and rightsizing resources to match workloads.\\nAccelerate App Development with Cloud Native Agility\\nOracle provides everything needed to build and deploy cloud native applications, including tooling, services, and automation, so that development teams can build quickly while reducing the number of operational tasks.\\nOracle cloud native services\\nrun on OCI, which offers a standards-based platform with higher performance and lower cost compared to other cloud providers. By taking advantage of services based on open source and open standards, OCI makes it possible for developers to run applications on any cloud or on-premises environment without refactoring. This flexibility provides the freedom to focus on building and innovating, such as with the help of powerful generative AI and even prebuilt AI\\/ML services, to breathe new capabilities and intelligence into your existing applications.\\nDoes cloud native application development truly deliver apps that are much better than traditionally developed apps? Yes. The benefits are clear: Cloud native apps can scale because their functions are broken into microservices, and they allow for individual management. What\\u2019s more, cloud native apps can run in a highly distributed manner, maintaining independence and allocating resources based on application needs.\\nCloud native applications can help strengthen business strategy and value because they can provide a consistent experience across private, public, and hybrid clouds. They allow your organization to take full advantage of cloud computing by running responsive and reliable scalable applications.\\nLooking to dig deeper into cloud native architectures? Download our free ebook to discover Any organization can adopt cloud native development strategies now.\\nAccess the ebook\\nCloud Native FAQs\\nHow does cloud native architecture differ from traditional application architectures?\\nCloud native architecture breaks large, complex business applications into many microservices, each of which performs a business function. The application works when these microservices communicate with one another over a high-speed network to collaborate on a task. Each microservice is defined, designed, built, tested, deployed, managed, and upgraded separately, which can result in faster deployments and much greater scalability. For example, when a microservice sees a high workload, a cloud native application can automatically make a copy of that microservice on a different server and split the workload between them. By contrast, a traditional application architecture consists of a single software code base\\u2014a monolith\\u2014that is designed, built, tested, and deployed as one unit. Bug fixes or upgrades result in changes to the monolith, which must then be redeployed. Because of this, software rollouts are often slow. Scalability is a challenge and often requires either rearchitecting (and rewriting) the software, or installing it on a faster, more expensive server.\\nHow can businesses effectively transition their existing applications to become cloud native?\\nExisting monolithic applications can be rearchitected into cloud native applications. The process is to identify parts of the code that can be split off into microservices, often beginning with the sections of code that are easiest to separate or are causing performance bottlenecks. By handling these sections one at a time, a monolithic application can realize many of the benefits of the cloud native approach.\\nWhat is the CNCF?\\nThe Cloud Native Computing Foundation (CNCF) is a vendor neutral open source organization hosted by the Linux Foundation. The CNCF\\u2019s goal is to promote cloud native technologies, and it provides essential support for many project and industry standards, such as the Docker container format and the Kubernetes container automation and orchestration platform. Many cloud services providers, including Oracle, contribute to the CNCF\\u2019s work and have adopted its standards to promote interoperability between cloud ecosystems.\\nWhat is the difference between cloud and cloud native?\\nCloud refers to computing services that are hosted by commercial service providers, such as Oracle. Those computing services include servers of many types, high-speed networks, storage systems, libraries of advanced computing functions (such as for AI and security), and even business applications. Nearly every website or application you access through a web browser is wholly or partially in the cloud; the rest reside in corporate data centers. Many mobile phone apps, too, rely on the cloud to provide essential functionality.\\nCloud native is an approach to building business applications that breaks up that application into dozens or hundreds of microservices. Each microservice encapsulates a key piece of business functionality. The application comes together to solve business problems when those microservices collaborate with each other over secure high-speed networks, with each microservice performing its own piece of the workload. Cloud native applications leverage a cloud services provider\\u2019s resources to make the application scalable, efficient, and resilient.\\nResources for\\nCareers\\nDevelopers\\nInvestors\\nPartners\\nStartups\\nStudents and Educators\\nWhy Oracle\\nAnalyst Reports\\nOCI | Microsoft Azure\\nCloud Reference Architectures\\nCorporate Responsibility\\nCulture and Inclusion\\nSecurity Practices\\nLearn\\nWhat is AI?\\nWhat is cloud computing?\\nWhat is Cloud Storage?\\nWhat is HPC?\\nWhat is IaaS?\\nWhat is PaaS?\\nWhat\\u2019s New\\nOracle Cloud Free Tier\\nCloud Architecture Center\\nCloud Lift\\nOracle Support Rewards\\nOracle Red Bull Racing\\nContact Us\\nSales: +44 207 5626 823\\nHow can we help?\\nSubscribe to emails\\nEvents\\nNews\\nOCI Blog\\nCountry\\/Region\\n\\u00a9 2026 Oracle\\nTerms of Use and Privacy\\nGender Pay Gap Report\\nModern Slavery Statement\\nAd Choices\\nCareers\\n\"}"
},
"response": {
"status": "ok",
"response": [
"Cloud native computing uses cloud platforms to design, create, deploy and run applications.",
"Cloud native apps use microservices (small pieces of software) in containers on cloud servers.",
"Microservices can be written, tested and deployed independently, making development faster.",
"Defects can be fixed in one microservice without affecting the whole application.",
"Overloaded microservices can be easily replicated to share the workload.",
"Developers can use the best tools and languages for each microservice.",
"Cloud Native Computing Foundation (CNCF) manages open standards for cloud native.",
"Cloud native enables scalable applications in public, private and hybrid clouds.",
"Containers hold microservices, and service meshes connect them.",
"Immutable infrastructure means containers are replaced, not modified.",
"Microservices communicate through well-defined protocols (APIs).",
"Cloud native apps can run in any cloud architecture (public, private, hybrid or multicloud).",
"DevOps teams use continuous integration (CI) and continuous delivery (CD).",
"Kubernetes automates deployment and management of containerised microservices.",
"Cloud native apps use resources better, reducing costs.",
"Docker is a common container standard.",
"Traditional apps are single codebases, updated by replacing the whole application.",
"Key components of cloud native development include:",
"Containers and containerisation for portable and rapid deployment",
"Microservices architecture for flexibility and faster development",
"Immutable infrastructure for consistency and easier rollbacks",
"Infrastructure-as-code (IaC) for automated provisioning",
"Automation and orchestration (e.g., Kubernetes) for scalability",
"Observability and monitoring for insights into performance",
"Resilience and self-healing for stability",
"Benefits of cloud native:",
"Scalability and flexibility to meet demand",
"Agile development and faster time to market",
"Cost efficiency through resource optimisation",
"Enhanced reliability and high availability",
"Seamless DevOps and CI/CD integration",
"Standards-based portability to reduce vendor lock-in",
"Integrated security at every layer",
"Challenges of cloud native:",
"Complexity, skills gaps and learning curve",
"Need for cultural shift towards DevOps",
"Security and compliance considerations",
"Managing distributed systems",
"Cost management",
"Best practices:",
"Adopt microservices architecture",
"Standardise on containers",
"Automate deployment and scaling",
"Use infrastructure as code (IaC)",
"Prioritise observability and monitoring",
"Integrate security at every layer",
"Optimise costs and resource utilisation",
"Oracle provides tools and services for cloud native applications on Oracle Cloud Infrastructure (OCI).",
"Cloud native apps scale well and manage resources efficiently.",
"Effective transition of existing apps can be achieved by rearchitecting monolithic applications by identifying code sections that can be split into microservices",
"Cloud native apps offer consistent experience across different cloud environments.",
"The CNCF promotes cloud native technologies, supporting standards like Docker and Kubernetes.",
"Cloud refers to computing services hosted by providers; cloud native is a way of building apps using cloud resources.",
"Sales contact number: +44 207 5626 823",
"The document was written on October 8, 2025",
"© 2026 Oracle"
]
}
} {
"prompt": {
"label": "is_firewall",
"prompt": {
"prompt_id": "6",
"prompt_label": "is_firewall",
"content_format": "{\"data\":\"content\"}",
"success_format": "{\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"}",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON.\nIgnore cookie requests in your judgment.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: {\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"} Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON. Ignore cookie requests in your judgment."
},
"content": "{\"data\":\"Project Calico\\nProducts\\nCalico Open Source\\neBPF-based networking and security\\nCalico Commercial Editions\\nCalico Cloud and Calico Enterprise\\nCompare Calico Editions\\nCalico Pricing\\nWhy Calico\\nSolutions\\nUse Cases\\nKubernetes Network Security\\nIngress Gateway\\nEgress Gateway\\nUniversal Firewall Integration\\nCluster Mesh\\nIstio Ambient Mode\\nCalico for AI Workloads\\nWorkload Access Controls\\nMicrosegmentation\\nHigh-Availability Kubernetes\\nObservability & Compliance\\nNetwork Threat Detection\\nSecurity Policy Management\\nObservability & Troubleshooting\\nCompliance\\nMulti-Cloud Security\\nEnvironments\\nAWS EKS\\nAzure AKS\\nGoogle GKE\\nRed Hat OpenShift\\nSUSE Rancher\\nFortinet\\nMirantis\\nLearn\\nDeveloper Center\\nDocumentation\\nInteractive Training\\nProduct Tutorials\\nCertification\\nEvents\\nResources\\nBlog\\nWhat Sets Calico Enterprise Apart\\nNEW\\nGet an independent breakdown of the networking, network security, and observability capabilities GigaOm evaluated for enterprise Kubernetes.\\nLearn More >\\nGuides\\nSecurity\\nKubernetes Security\\nLLM Security\\nService Mesh\\nMicroservices Security\\nZero Trust\\nCloud-Native Security\\nMicrosegmentation\\nGuides\\nObservability\\nObservability\\nKubernetes Monitoring\\nPrometheus Monitoring\\nNetworking\\nKubernetes Networking\\nCillium vs Calico\\neBPF\\nSupport\\nCustomer Success\\nSupport Portal\\nTigera Help Center\\nSecurity Bulletins\\nReport Security Issue\\nCompany\\nAbout\\nCalicoCon 2025\\nCustomers\\nPartners\\nNewsroom\\nCareers\\nContact\\nContact\\nLogin\\nStart Free\\nGuides: What is Cloud Native\\nWhat Is Cloud Native: Principles, Pros, Cons and Best Practices\\nCloud-Native Security\\nWhat is Cloud Native\\nCloud Native Networking\\nCloud Native Architecture\\nCloud-Native Monitoring\\nWhat Is Cloud Native?\\nCloud native refers to a software development approach focused on building and running applications in modern, dynamic, and distributed cloud environments. It uses technologies like microservices, containers, and container orchestration (like Kubernetes) to create scalable, resilient, and easily manageable applications.\\nCloud native applications are designed to fully utilize the capabilities of cloud platforms, enabling faster development cycles, increased agility, and improved operational efficiency.\\nKey characteristics of cloud native applications include:\\nMicroservices architecture:\\nApplications are broken down into small, independent, and loosely coupled services, each performing a specific function.\\nContainer orchestration:\\nTools like Kubernetes automate the deployment, scaling, and management of containers, ensuring high availability and fault tolerance.\\nImmutable infrastructure:\\nChanges to infrastructure are infrequent, and new versions of applications are deployed by replacing the entire existing infrastructure with a new one, ensuring consistency and reducing the risk of errors.\\nAutomation:\\nCloud native architectures embrace automation throughout the development and deployment lifecycle, using DevOps practices like CI\\/CD (Continuous Integration\\/Continuous Delivery).\\nResilience:\\nCloud native applications are designed to be resilient, with self-healing capabilities and automated failover mechanisms, ensuring minimal downtime.\\nScalability:\\nCloud native applications can easily scale up or down based on demand, leveraging the elasticity of cloud platforms.\\nPortability:\\nCloud native applications are designed to be portable across different cloud providers or on-premises environments, thanks to containerization and orchestration.\\nKey benefits of cloud native include:\\nFaster development and deployment:\\nMicroservices and containers allow for faster development cycles and more frequent updates.\\nIncreased agility:\\nCloud native architectures enable organizations to respond quickly to changing business needs and market demands.\\nImproved scalability and availability:\\nCloud native applications can scale to handle fluctuating traffic and ensure high availability.\\nReduced operational costs:\\nAutomation and efficient resource utilization can lead to lower operational costs.\\nEnhanced innovation:\\nCloud native technologies foster a culture of innovation and experimentation, allowing teams to try new ideas and technologies quickly.\\nThis is part of a series of articles about\\ncloud native security.\\nIn this article:\\n7 Key Principles and Characteristics of Cloud Native\\nPros and Cons of Cloud Native\\nCloud Native vs. Cloud-Based\\nKey Use Cases of Cloud Native Applications\\nBest Practices for Cloud Native Implementation\\n7 Key Principles and Characteristics of Cloud Native\\nCloud native applications are defined by a set of principles and architectural patterns that enable them to fully leverage cloud environments. The following characteristics outline the technical foundation and operational practices that distinguish cloud native systems from traditional approaches.\\nMicroservices architecture:\\nCloud native applications are composed of loosely coupled services, each responsible for a specific business function. This modular approach enables independent development, deployment, and scaling of services, leading to greater agility and maintainability.\\nContainerization:\\nContainers provide a lightweight and consistent execution environment across development, testing, and production. Tools like Docker and Kubernetes standardize how applications are packaged and deployed, simplifying scalability and operations.\\nDynamic orchestration:\\nPlatforms such as Kubernetes automate the deployment, scaling, and management of containerized applications. This ensures efficient resource usage and high availability, as workloads are automatically distributed and recovered in case of failures.\\nDeclarative APIs and configuration:\\nCloud native systems use declarative definitions to describe infrastructure and application states. This approach improves repeatability, reduces errors, and integrates well with version control systems for better traceability and automation.\\nAutomation (DevOps and CI\\/CD practices):\\nCloud native promotes automation in building, testing, and deploying applications. Continuous integration and delivery pipelines shorten release cycles and enable faster feedback, enhancing responsiveness to business needs.\\nResilience and observability:\\nFailure is expected and managed gracefully in cloud native environments. Applications are built with fault tolerance and self-healing in mind, while tools for logging, monitoring, and tracing provide the visibility needed to detect and resolve issues quickly.\\nScalability and elasticity:\\nCloud native applications are designed to scale horizontally. They can handle variable loads by dynamically adjusting resource usage, ensuring performance without overprovisioning.\\nPortability:\\nCloud native applications are built to run consistently across different cloud providers and on-premises environments. By using containers, declarative configuration, and standardized APIs, teams can deploy workloads without being tightly coupled to one vendor\\u2019s infrastructure.\\nPros and Cons of Cloud Native\\nCloud native offers compelling advantages for organizations aiming to accelerate innovation and improve operational efficiency. However, adopting this approach also introduces new complexities and challenges that teams must be prepared to manage.\\nPros of cloud native:\\nScalability:\\nApplications can scale horizontally to meet demand, improving performance and cost-efficiency.\\nResilience:\\nBuilt-in fault tolerance and self-healing reduce downtime and improve system reliability.\\nFaster delivery:\\nCI\\/CD pipelines and DevOps practices enable rapid development and deployment cycles.\\nPortability:\\nContainerization and standardized APIs make it easier to move workloads across environments.\\nResource optimization:\\nDynamic orchestration ensures efficient use of computing resources, lowering infrastructure costs.\\nImproved collaboration:\\nCloud native encourages cross-functional teams and automation, enhancing coordination and productivity.\\nCons of cloud native:\\nComplexity:\\nManaging distributed systems, orchestration platforms, and service dependencies can be challenging.\\nSteep learning curve:\\nTeams may need significant upskilling in tools like Kubernetes, containers, and CI\\/CD practices.\\nIncreased operational overhead:\\nMonitoring, security, and observability require new tools and processes.\\nCost management difficulties:\\nWhile scalable, uncontrolled usage of cloud resources can lead to unexpected expenses.\\nVendor lock-in risks:\\nHeavy reliance on specific cloud services or platforms may limit flexibility in the long term.\\nSecurity challenges:\\nDistributed and containerized environments introduce new attack surfaces and compliance issues.\\nCloud Native vs. Cloud-Based\\nThe terms \\u201ccloud native\\u201d and \\u201ccloud-based\\u201d are often used interchangeably, but they refer to different architectural and operational models.\\nCloud-based applications\\nare typically legacy systems or traditional software that have been migrated to run on cloud infrastructure. These applications may still follow monolithic designs and often require manual scaling and management. While they benefit from some cloud capabilities\\u2014like hosted infrastructure or managed services\\u2014they are not optimized to fully leverage the cloud\\u2019s dynamic nature.\\nCloud native applications\\nare built specifically for the cloud from the ground up. They are designed to be scalable, resilient, and portable by using microservices, containers, orchestration tools, and automated pipelines. These systems can dynamically adapt to load changes, recover from failures automatically, and are often deployed through CI\\/CD workflows.\\nTips from the Expert\\nIn my experience, here are tips that can help you better adopt and operationalize cloud native architectures beyond what the article covered:\\nAdopt a service ownership model early:\\nEstablish a clear ownership model where each microservice has a dedicated owner team responsible for its full lifecycle (development, deployment, monitoring, and incident response). This improves accountability and ensures faster resolution times for service-related issues.\\nImplement network segmentation using Kubernetes Network Policies:\\nAvoid flat network architectures by applying Kubernetes Network Policies or service mesh-level controls to segment communication between microservices. This limits lateral movement in case of a breach.\\nIntegrate policy-as-code for cloud native security governance:\\nUse tools like Open Policy Agent (OPA) or Kyverno to enforce security and compliance policies (e.g., restricting privilege escalation, enforcing image provenance) as code at deployment time.\\nRun workload-specific vulnerability scans pre-deployment:\\nGo beyond general image scanning. Conduct runtime behavioral analysis or sandboxing (e.g., dynamic malware analysis) for critical container images before allowing them into production.\\nUse horizontal pod autoscaling based on custom metrics:\\nInstead of scaling based only on CPU\\/memory, configure Horizontal Pod Autoscalers (HPA) to react to application-specific custom metrics (like queue length or request latency) for more intelligent scaling.\\nPeter Kelly\\nVP of Engineering\\nPeter Kelly is VP of Engineering at Tigera and Site Leader for Tigera's EMEA office in Cork, Ireland. He is responsible for all of Tigera\\u2019s Engineering teams and operations. Peter has two decades of experience in software development, including recently building control plane technology for open-source proxies at NGINX and later F5 Networks, where he held engineering leadership positions.\\r\\n\\r\\nPeter has a degree in Computer Science and a Masters in Advanced Software Engineering.\\nKey Use Cases of Cloud Native Applications\\nDevOps and CI\\/CD\\nCloud native tooling and architectures are tightly integrated with DevOps practices and continuous integration\\/continuous delivery (CI\\/CD) pipelines. These pipelines automate the testing, building, and deployment of code, enabling teams to deliver software faster and with greater reliability. By utilizing containers and microservices, developers can roll out updates independently, minimizing downtime and reducing the risk of widespread failure.\\nThis approach supports rapid experimentation and innovation. Automated rollbacks, blue-green deployments, and canary releases are common methods made more reliable and easier to manage in a cloud native environment. The result is improved collaboration between development and operations teams, streamlined releases, and the ability to resolve issues or roll out new features on demand, aligning software development more closely with business objectives.\\nLegacy Modernization\\nMany organizations use cloud native strategies to modernize legacy applications. This often involves decomposing monolithic applications into microservices or re-platforming them into containers, enabling gradual but systematic migration to the cloud. The process increases flexibility, making it easier to scale, update, and manage functionality as business requirements evolve.\\nLegacy modernization via cloud native not only extends the lifespan of existing systems but also enhances security, reliability, and maintainability. Old systems gain access to modern development tools, orchestration, and monitoring, reducing technical debt and operational risk. By adopting cloud native patterns, enterprises can innovate faster and respond to customer and market demands more effectively while protecting their investment in core business logic.\\nService Mesh and Messaging\\nService meshes are a key enabler in\\ncloud native architectures\\n, providing a critical control layer for inter-service communication. Technologies like Istio, Linkerd, or Consul manage secure service-to-service networking, load balancing, and observability, abstracting these concerns away from application code. This increases reliability and simplifies operations across distributed microservices.\\nMessaging is another frequent use case, with cloud native platforms supporting scalable event-driven architectures. Modern cloud environments often use tools like Apache Kafka, RabbitMQ, or cloud provider messaging services to build loosely coupled systems that react to events in real time. This approach enhances system responsiveness, simplifies integrations, and allows applications to scale independently, strengthening agility and fault tolerance.\\nMedia and Streaming\\nCloud native patterns are well-suited for media delivery and streaming services that require dynamic scalability and robust availability. Containers and orchestration platforms allow media processing workloads\\u2014such as video encoding or real-time streaming\\u2014to be spun up or down quickly according to user demand, reducing costs and improving efficiency.\\nThese workloads benefit from decentralized architectures and distributed storage, enabling high-throughput, low-latency delivery across global audiences. Cloud native solutions frequently make use of content delivery networks (CDNs), cloud-based storage, and automated scaling, ensuring a seamless viewing or listening experience. As user expectations for uninterrupted service grow, media companies rely on cloud native architectures to meet these requirements reliably.\\nBest Practices for Cloud Native Implementation\\n1. Design for Resilience and Failover.\\nBuilding resilience into cloud native systems requires architecting for failure from the outset. Services should be stateless where possible, allowing them to be redeployed or restarted without loss of critical data. Redundancy through container replicas, multi-zone or multi-region deployment, and health checks improve survivability and minimize downtime. Robust failover mechanisms ensure that workloads are automatically redirected in the event of an outage or resource failure.\\nImplementing patterns like circuit breakers, retries with exponential backoff, and graceful degradation prevents cascading failures and maintains overall system functionality even when individual components misbehave. Resilience testing, including chaos engineering and disaster recovery drills, further validates system robustness. Designing for resilience is not a one-time event but a continuous process, adapting to new threats and operational insights.\\n2. Implement DevSecOps\\nDevSecOps is the practice of integrating security practices within the DevOps process, making security an ongoing and automated part of application development and deployment. This ensures vulnerabilities are detected earlier, compliance is maintained, and risk is minimized as applications evolve. Implementing automated security testing in CI\\/CD pipelines\\u2014covering static code analysis, dependency scanning, and runtime protections\\u2014is essential to reduce the manual burden and increase effectiveness.\\nCollaboration between security, development, and operations teams becomes central for a successful DevSecOps approach. This includes clear security guidelines, regular threat modeling, and post-mortem analyses of incidents. When security becomes everyone\\u2019s responsibility\\u2014and is proactively automated throughout the build and deployment stages\\u2014cloud native environments become significantly more resilient against evolving threats.\\n3. Leverage Cloud Load Balancers and Ingress Controllers\\nAutomated load balancing distributes network traffic among compute resources to maximize throughput, minimize response time, and prevent overload. In cloud native architectures, built-in load balancers and ingress controllers handle dynamic routing, SSL termination, and traffic splitting, allowing services to scale seamlessly and applications to remain available even during peak loads.\\nThese tools also simplify the exposure of microservices to external consumers by managing traffic policies, authentication, and security controls centrally. Fine-tuned configurations, blue-green deployments, and A\\/B testing strategies are easier to implement with sophisticated ingress controllers. Organizations that leverage these mechanisms reduce operational overhead and improve the performance and reliability of cloud native applications.\\n4. Use GitOps Practices\\nGitOps is a paradigm that uses git repositories as the single source of truth for declarative infrastructure and application configurations. Changes to infrastructure or application state are managed via pull requests, ensuring all modifications are versioned, audited, and easily rolled back if needed. This fosters transparency, reliability, and repeatability across development and operations.\\nThe automated reconciliation process of GitOps tools observes the git state and enforces it within the production environment, reducing configuration drift and manual errors. GitOps accelerates onboarding for new team members and enables rapid, safe rollbacks in case of issues. Adopting GitOps practices results in faster development cycles, better operational control, and improved compliance, all critical to high-performing cloud native environments.\\n5. Ensure Comprehensive Monitoring\\nComprehensive monitoring provides visibility into all layers of a cloud native stack, from application metrics and logs to infrastructure health and network traffic patterns. Dashboards and automated alerts help teams detect anomalies, diagnose root causes, and respond proactively to performance degradations or outages.\\nCloud native monitoring\\nleverages tools like Prometheus, Grafana, and commercial observability platforms for granular insight.\\nEnd-to-end observability is necessary for troubleshooting distributed systems, ensuring compliance, and planning system enhancements. Tracing transactions across microservices, monitoring for security incidents, and logging user interactions allow for rapid incident response and continuous improvement. Robust monitoring practices are foundational for operational excellence, supporting reliability and scalability goals in cloud native systems.\\nReal-world example:\\nPrivate health insurance company HanseMerkur, used Calico to reduce infrastructure overhead and meet ISO 27001 compliance standards. The platform\\u2019s unified observability helped the team simplify security operations while gaining visibility into critical workloads across Kubernetes environments.\\nClick here to read the HanseMerkur case study.\\u00a0\\nCloud Native Networking, Security, and Observability with Calico\\nCalico provides a comprehensive set of capabilities purpose-built for cloud native environments, combining scalable networking, fine-grained security controls, and deep observability across Kubernetes clusters. Whether operating in single or multi-cluster environments, Calico empowers platform, security, and DevOps teams to deliver secure, reliable, and high-performance applications at scale.\\nHow Calico Supports Cloud Native Networking\\nHigh-Performance Data Planes\\nCalico supports multiple data planes\\u2014including eBPF, iptables, nftables, and VPP\\u2014enabling teams to choose the best option for performance, compatibility, and operational visibility. The eBPF data plane delivers low latency, high throughput, and efficient resource usage, making it ideal for high-scale production environments.\\nMulti-Cluster and Hybrid Connectivity\\nCalico enables resilient pod-to-pod communication across clusters and supports a wide range of environments including cloud, on-premises, and bare metal. Multi-cluster service connectivity and cluster mesh capabilities ensure seamless workload interoperability and simplified application delivery across diverse infrastructures.\\nIngress and Egress Gateways\\nCalico provides robust ingress and egress gateway capabilities, allowing teams to securely manage external communication. Egress gateways enable fixed, routable IPs for outbound traffic, supporting compliance and firewall configurations. Ingress gateways provide centralized control for managing incoming traffic using standard Kubernetes APIs.\\nHow Calico Supports Network Security in Kubernetes\\nFine-Grained Network Policy Control\\nCalico extends native Kubernetes NetworkPolicy with advanced capabilities such as global policies, policy tiers, and DNS-based rules. Teams can define security policies that span across namespaces or clusters, supporting both L3\\/L4 and application-aware L7 enforcement.\\nMicrosegmentation and Threat Prevention\\nBuilt-in microsegmentation capabilities allow teams to isolate workloads and limit lateral movement, reducing the blast radius of potential attacks. Calico also supports data-in-transit encryption with WireGuard, intrusion detection and prevention (IDS\\/IPS), and protections against DDoS and web application threats.\\nPolicy Lifecycle Management\\nSecurity policies can be staged, previewed, and tested before enforcement, reducing the risk of disruptions. Calico enables a policy-as-code approach that integrates with CI\\/CD pipelines, ensuring security policies are version-controlled and aligned with application delivery workflows.\\nHow Calico Enhances Observability for Cloud Native Operations\\nReal-Time Service and Threat Graphs\\nCalico provides dynamic, interactive visualizations of service-to-service communication, network flows, and policy enforcement. These graphs help teams quickly understand dependencies, identify anomalies, and respond to threats or misconfigurations across workloads and namespaces.\\nDeep Protocol and Application-Level Visibility\\nCalico delivers L7 observability without requiring a full service mesh, offering insight into HTTP traffic patterns, response codes, request latency, and endpoint behavior. DNS dashboards provide workload-aware visibility into DNS activity, making it easier to detect misconfigurations and abnormal query patterns.\\nTargeted Troubleshooting and Root Cause Analysis\\nAdvanced tools such as dynamic packet capture and flow visualizers enable precise, on-demand debugging without disrupting production. These features accelerate incident response by providing direct access to traffic data at the pod or node level.\\nCentralized Monitoring and Compliance Reporting\\nCalico aggregates enriched logs, metrics, and policy data across clusters into unified dashboards. Teams can monitor network behavior, track policy compliance, and export data to external systems for further analysis. Automated compliance reporting supports standards such as PCI DSS, HIPAA, and SOC 2.\\n\\u00a0\\nReal-World Example:\\nBox, a cloud content management and file sharing company, adopted Calico to implement zero-trust security and policy automation at scale across multi-cluster environments. Calico\\u2019s observability capabilities provided Box with real-time visibility into workload communication and policy behaviour, significantly accelerating incident response and simplifying policy troubleshooting across clusters.\\nClick here to read the full case study.\\nNext Steps:\\nEnforcing workload isolation and segmentation in Kubernetes using Calico\\nIntegrating Calico security policies into DevSecOps workflows\\nMonitoring Kubernetes network traffic with Calico dashboards\\nPROJECT CALICO\\nWhat is Project Calico?\\nDocs\\nCommunity\\nGitHub\\nPRODUCTS\\nCalico Open Source\\nCalico Commercial Editions\\nCompare Calico Editions\\nPricing\\nWhy Calico?\\nSOLUTIONS\\nIngress Gateway\\nEgress Gateway\\nCluster Mesh\\nMulti-Cloud Security\\nObservability & Troubleshooting\\nCompliance\\nMicrosegmentation\\nEnvironments\\nLEARN\\nDocumentation\\nInteractive Training\\nProduct Tutorials\\nCertification\\nEvents\\nResources\\nBlog\\nGuides\\nSUPPORT\\nCustomer Success\\nSupport Portal\\nTigera Help Center\\nSecurity Bulletins\\nReport Security Issue\\nCOMPANY\\nAbout\\nCalicoCon 2025\\nCustomers\\nPartners\\nNewsroom\\nCareers\\nContact\\nCopyright \\u00a9\\nTigera, Inc. All rights reserved.\\nPrivacy Center\\nDo Not Sell Or Share My Personal Information\\nLegal\\nLinkedin\\nTwitter\\nYoutube\\nSlack\\nGithub\\nDiscourse\\n\"}"
},
"response": {
"status": "false",
"response": "false"
}
} {
"prompt": {
"label": "resume_data",
"prompt": {
"prompt_id": "7",
"prompt_label": "resume_data",
"content_format": "{\"data\":\"content\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you."
},
"content": "{\"data\":\"Project Calico\\nProducts\\nCalico Open Source\\neBPF-based networking and security\\nCalico Commercial Editions\\nCalico Cloud and Calico Enterprise\\nCompare Calico Editions\\nCalico Pricing\\nWhy Calico\\nSolutions\\nUse Cases\\nKubernetes Network Security\\nIngress Gateway\\nEgress Gateway\\nUniversal Firewall Integration\\nCluster Mesh\\nIstio Ambient Mode\\nCalico for AI Workloads\\nWorkload Access Controls\\nMicrosegmentation\\nHigh-Availability Kubernetes\\nObservability & Compliance\\nNetwork Threat Detection\\nSecurity Policy Management\\nObservability & Troubleshooting\\nCompliance\\nMulti-Cloud Security\\nEnvironments\\nAWS EKS\\nAzure AKS\\nGoogle GKE\\nRed Hat OpenShift\\nSUSE Rancher\\nFortinet\\nMirantis\\nLearn\\nDeveloper Center\\nDocumentation\\nInteractive Training\\nProduct Tutorials\\nCertification\\nEvents\\nResources\\nBlog\\nWhat Sets Calico Enterprise Apart\\nNEW\\nGet an independent breakdown of the networking, network security, and observability capabilities GigaOm evaluated for enterprise Kubernetes.\\nLearn More >\\nGuides\\nSecurity\\nKubernetes Security\\nLLM Security\\nService Mesh\\nMicroservices Security\\nZero Trust\\nCloud-Native Security\\nMicrosegmentation\\nGuides\\nObservability\\nObservability\\nKubernetes Monitoring\\nPrometheus Monitoring\\nNetworking\\nKubernetes Networking\\nCillium vs Calico\\neBPF\\nSupport\\nCustomer Success\\nSupport Portal\\nTigera Help Center\\nSecurity Bulletins\\nReport Security Issue\\nCompany\\nAbout\\nCalicoCon 2025\\nCustomers\\nPartners\\nNewsroom\\nCareers\\nContact\\nContact\\nLogin\\nStart Free\\nGuides: What is Cloud Native\\nWhat Is Cloud Native: Principles, Pros, Cons and Best Practices\\nCloud-Native Security\\nWhat is Cloud Native\\nCloud Native Networking\\nCloud Native Architecture\\nCloud-Native Monitoring\\nWhat Is Cloud Native?\\nCloud native refers to a software development approach focused on building and running applications in modern, dynamic, and distributed cloud environments. It uses technologies like microservices, containers, and container orchestration (like Kubernetes) to create scalable, resilient, and easily manageable applications.\\nCloud native applications are designed to fully utilize the capabilities of cloud platforms, enabling faster development cycles, increased agility, and improved operational efficiency.\\nKey characteristics of cloud native applications include:\\nMicroservices architecture:\\nApplications are broken down into small, independent, and loosely coupled services, each performing a specific function.\\nContainer orchestration:\\nTools like Kubernetes automate the deployment, scaling, and management of containers, ensuring high availability and fault tolerance.\\nImmutable infrastructure:\\nChanges to infrastructure are infrequent, and new versions of applications are deployed by replacing the entire existing infrastructure with a new one, ensuring consistency and reducing the risk of errors.\\nAutomation:\\nCloud native architectures embrace automation throughout the development and deployment lifecycle, using DevOps practices like CI\\/CD (Continuous Integration\\/Continuous Delivery).\\nResilience:\\nCloud native applications are designed to be resilient, with self-healing capabilities and automated failover mechanisms, ensuring minimal downtime.\\nScalability:\\nCloud native applications can easily scale up or down based on demand, leveraging the elasticity of cloud platforms.\\nPortability:\\nCloud native applications are designed to be portable across different cloud providers or on-premises environments, thanks to containerization and orchestration.\\nKey benefits of cloud native include:\\nFaster development and deployment:\\nMicroservices and containers allow for faster development cycles and more frequent updates.\\nIncreased agility:\\nCloud native architectures enable organizations to respond quickly to changing business needs and market demands.\\nImproved scalability and availability:\\nCloud native applications can scale to handle fluctuating traffic and ensure high availability.\\nReduced operational costs:\\nAutomation and efficient resource utilization can lead to lower operational costs.\\nEnhanced innovation:\\nCloud native technologies foster a culture of innovation and experimentation, allowing teams to try new ideas and technologies quickly.\\nThis is part of a series of articles about\\ncloud native security.\\nIn this article:\\n7 Key Principles and Characteristics of Cloud Native\\nPros and Cons of Cloud Native\\nCloud Native vs. Cloud-Based\\nKey Use Cases of Cloud Native Applications\\nBest Practices for Cloud Native Implementation\\n7 Key Principles and Characteristics of Cloud Native\\nCloud native applications are defined by a set of principles and architectural patterns that enable them to fully leverage cloud environments. The following characteristics outline the technical foundation and operational practices that distinguish cloud native systems from traditional approaches.\\nMicroservices architecture:\\nCloud native applications are composed of loosely coupled services, each responsible for a specific business function. This modular approach enables independent development, deployment, and scaling of services, leading to greater agility and maintainability.\\nContainerization:\\nContainers provide a lightweight and consistent execution environment across development, testing, and production. Tools like Docker and Kubernetes standardize how applications are packaged and deployed, simplifying scalability and operations.\\nDynamic orchestration:\\nPlatforms such as Kubernetes automate the deployment, scaling, and management of containerized applications. This ensures efficient resource usage and high availability, as workloads are automatically distributed and recovered in case of failures.\\nDeclarative APIs and configuration:\\nCloud native systems use declarative definitions to describe infrastructure and application states. This approach improves repeatability, reduces errors, and integrates well with version control systems for better traceability and automation.\\nAutomation (DevOps and CI\\/CD practices):\\nCloud native promotes automation in building, testing, and deploying applications. Continuous integration and delivery pipelines shorten release cycles and enable faster feedback, enhancing responsiveness to business needs.\\nResilience and observability:\\nFailure is expected and managed gracefully in cloud native environments. Applications are built with fault tolerance and self-healing in mind, while tools for logging, monitoring, and tracing provide the visibility needed to detect and resolve issues quickly.\\nScalability and elasticity:\\nCloud native applications are designed to scale horizontally. They can handle variable loads by dynamically adjusting resource usage, ensuring performance without overprovisioning.\\nPortability:\\nCloud native applications are built to run consistently across different cloud providers and on-premises environments. By using containers, declarative configuration, and standardized APIs, teams can deploy workloads without being tightly coupled to one vendor\\u2019s infrastructure.\\nPros and Cons of Cloud Native\\nCloud native offers compelling advantages for organizations aiming to accelerate innovation and improve operational efficiency. However, adopting this approach also introduces new complexities and challenges that teams must be prepared to manage.\\nPros of cloud native:\\nScalability:\\nApplications can scale horizontally to meet demand, improving performance and cost-efficiency.\\nResilience:\\nBuilt-in fault tolerance and self-healing reduce downtime and improve system reliability.\\nFaster delivery:\\nCI\\/CD pipelines and DevOps practices enable rapid development and deployment cycles.\\nPortability:\\nContainerization and standardized APIs make it easier to move workloads across environments.\\nResource optimization:\\nDynamic orchestration ensures efficient use of computing resources, lowering infrastructure costs.\\nImproved collaboration:\\nCloud native encourages cross-functional teams and automation, enhancing coordination and productivity.\\nCons of cloud native:\\nComplexity:\\nManaging distributed systems, orchestration platforms, and service dependencies can be challenging.\\nSteep learning curve:\\nTeams may need significant upskilling in tools like Kubernetes, containers, and CI\\/CD practices.\\nIncreased operational overhead:\\nMonitoring, security, and observability require new tools and processes.\\nCost management difficulties:\\nWhile scalable, uncontrolled usage of cloud resources can lead to unexpected expenses.\\nVendor lock-in risks:\\nHeavy reliance on specific cloud services or platforms may limit flexibility in the long term.\\nSecurity challenges:\\nDistributed and containerized environments introduce new attack surfaces and compliance issues.\\nCloud Native vs. Cloud-Based\\nThe terms \\u201ccloud native\\u201d and \\u201ccloud-based\\u201d are often used interchangeably, but they refer to different architectural and operational models.\\nCloud-based applications\\nare typically legacy systems or traditional software that have been migrated to run on cloud infrastructure. These applications may still follow monolithic designs and often require manual scaling and management. While they benefit from some cloud capabilities\\u2014like hosted infrastructure or managed services\\u2014they are not optimized to fully leverage the cloud\\u2019s dynamic nature.\\nCloud native applications\\nare built specifically for the cloud from the ground up. They are designed to be scalable, resilient, and portable by using microservices, containers, orchestration tools, and automated pipelines. These systems can dynamically adapt to load changes, recover from failures automatically, and are often deployed through CI\\/CD workflows.\\nTips from the Expert\\nIn my experience, here are tips that can help you better adopt and operationalize cloud native architectures beyond what the article covered:\\nAdopt a service ownership model early:\\nEstablish a clear ownership model where each microservice has a dedicated owner team responsible for its full lifecycle (development, deployment, monitoring, and incident response). This improves accountability and ensures faster resolution times for service-related issues.\\nImplement network segmentation using Kubernetes Network Policies:\\nAvoid flat network architectures by applying Kubernetes Network Policies or service mesh-level controls to segment communication between microservices. This limits lateral movement in case of a breach.\\nIntegrate policy-as-code for cloud native security governance:\\nUse tools like Open Policy Agent (OPA) or Kyverno to enforce security and compliance policies (e.g., restricting privilege escalation, enforcing image provenance) as code at deployment time.\\nRun workload-specific vulnerability scans pre-deployment:\\nGo beyond general image scanning. Conduct runtime behavioral analysis or sandboxing (e.g., dynamic malware analysis) for critical container images before allowing them into production.\\nUse horizontal pod autoscaling based on custom metrics:\\nInstead of scaling based only on CPU\\/memory, configure Horizontal Pod Autoscalers (HPA) to react to application-specific custom metrics (like queue length or request latency) for more intelligent scaling.\\nPeter Kelly\\nVP of Engineering\\nPeter Kelly is VP of Engineering at Tigera and Site Leader for Tigera's EMEA office in Cork, Ireland. He is responsible for all of Tigera\\u2019s Engineering teams and operations. Peter has two decades of experience in software development, including recently building control plane technology for open-source proxies at NGINX and later F5 Networks, where he held engineering leadership positions.\\r\\n\\r\\nPeter has a degree in Computer Science and a Masters in Advanced Software Engineering.\\nKey Use Cases of Cloud Native Applications\\nDevOps and CI\\/CD\\nCloud native tooling and architectures are tightly integrated with DevOps practices and continuous integration\\/continuous delivery (CI\\/CD) pipelines. These pipelines automate the testing, building, and deployment of code, enabling teams to deliver software faster and with greater reliability. By utilizing containers and microservices, developers can roll out updates independently, minimizing downtime and reducing the risk of widespread failure.\\nThis approach supports rapid experimentation and innovation. Automated rollbacks, blue-green deployments, and canary releases are common methods made more reliable and easier to manage in a cloud native environment. The result is improved collaboration between development and operations teams, streamlined releases, and the ability to resolve issues or roll out new features on demand, aligning software development more closely with business objectives.\\nLegacy Modernization\\nMany organizations use cloud native strategies to modernize legacy applications. This often involves decomposing monolithic applications into microservices or re-platforming them into containers, enabling gradual but systematic migration to the cloud. The process increases flexibility, making it easier to scale, update, and manage functionality as business requirements evolve.\\nLegacy modernization via cloud native not only extends the lifespan of existing systems but also enhances security, reliability, and maintainability. Old systems gain access to modern development tools, orchestration, and monitoring, reducing technical debt and operational risk. By adopting cloud native patterns, enterprises can innovate faster and respond to customer and market demands more effectively while protecting their investment in core business logic.\\nService Mesh and Messaging\\nService meshes are a key enabler in\\ncloud native architectures\\n, providing a critical control layer for inter-service communication. Technologies like Istio, Linkerd, or Consul manage secure service-to-service networking, load balancing, and observability, abstracting these concerns away from application code. This increases reliability and simplifies operations across distributed microservices.\\nMessaging is another frequent use case, with cloud native platforms supporting scalable event-driven architectures. Modern cloud environments often use tools like Apache Kafka, RabbitMQ, or cloud provider messaging services to build loosely coupled systems that react to events in real time. This approach enhances system responsiveness, simplifies integrations, and allows applications to scale independently, strengthening agility and fault tolerance.\\nMedia and Streaming\\nCloud native patterns are well-suited for media delivery and streaming services that require dynamic scalability and robust availability. Containers and orchestration platforms allow media processing workloads\\u2014such as video encoding or real-time streaming\\u2014to be spun up or down quickly according to user demand, reducing costs and improving efficiency.\\nThese workloads benefit from decentralized architectures and distributed storage, enabling high-throughput, low-latency delivery across global audiences. Cloud native solutions frequently make use of content delivery networks (CDNs), cloud-based storage, and automated scaling, ensuring a seamless viewing or listening experience. As user expectations for uninterrupted service grow, media companies rely on cloud native architectures to meet these requirements reliably.\\nBest Practices for Cloud Native Implementation\\n1. Design for Resilience and Failover.\\nBuilding resilience into cloud native systems requires architecting for failure from the outset. Services should be stateless where possible, allowing them to be redeployed or restarted without loss of critical data. Redundancy through container replicas, multi-zone or multi-region deployment, and health checks improve survivability and minimize downtime. Robust failover mechanisms ensure that workloads are automatically redirected in the event of an outage or resource failure.\\nImplementing patterns like circuit breakers, retries with exponential backoff, and graceful degradation prevents cascading failures and maintains overall system functionality even when individual components misbehave. Resilience testing, including chaos engineering and disaster recovery drills, further validates system robustness. Designing for resilience is not a one-time event but a continuous process, adapting to new threats and operational insights.\\n2. Implement DevSecOps\\nDevSecOps is the practice of integrating security practices within the DevOps process, making security an ongoing and automated part of application development and deployment. This ensures vulnerabilities are detected earlier, compliance is maintained, and risk is minimized as applications evolve. Implementing automated security testing in CI\\/CD pipelines\\u2014covering static code analysis, dependency scanning, and runtime protections\\u2014is essential to reduce the manual burden and increase effectiveness.\\nCollaboration between security, development, and operations teams becomes central for a successful DevSecOps approach. This includes clear security guidelines, regular threat modeling, and post-mortem analyses of incidents. When security becomes everyone\\u2019s responsibility\\u2014and is proactively automated throughout the build and deployment stages\\u2014cloud native environments become significantly more resilient against evolving threats.\\n3. Leverage Cloud Load Balancers and Ingress Controllers\\nAutomated load balancing distributes network traffic among compute resources to maximize throughput, minimize response time, and prevent overload. In cloud native architectures, built-in load balancers and ingress controllers handle dynamic routing, SSL termination, and traffic splitting, allowing services to scale seamlessly and applications to remain available even during peak loads.\\nThese tools also simplify the exposure of microservices to external consumers by managing traffic policies, authentication, and security controls centrally. Fine-tuned configurations, blue-green deployments, and A\\/B testing strategies are easier to implement with sophisticated ingress controllers. Organizations that leverage these mechanisms reduce operational overhead and improve the performance and reliability of cloud native applications.\\n4. Use GitOps Practices\\nGitOps is a paradigm that uses git repositories as the single source of truth for declarative infrastructure and application configurations. Changes to infrastructure or application state are managed via pull requests, ensuring all modifications are versioned, audited, and easily rolled back if needed. This fosters transparency, reliability, and repeatability across development and operations.\\nThe automated reconciliation process of GitOps tools observes the git state and enforces it within the production environment, reducing configuration drift and manual errors. GitOps accelerates onboarding for new team members and enables rapid, safe rollbacks in case of issues. Adopting GitOps practices results in faster development cycles, better operational control, and improved compliance, all critical to high-performing cloud native environments.\\n5. Ensure Comprehensive Monitoring\\nComprehensive monitoring provides visibility into all layers of a cloud native stack, from application metrics and logs to infrastructure health and network traffic patterns. Dashboards and automated alerts help teams detect anomalies, diagnose root causes, and respond proactively to performance degradations or outages.\\nCloud native monitoring\\nleverages tools like Prometheus, Grafana, and commercial observability platforms for granular insight.\\nEnd-to-end observability is necessary for troubleshooting distributed systems, ensuring compliance, and planning system enhancements. Tracing transactions across microservices, monitoring for security incidents, and logging user interactions allow for rapid incident response and continuous improvement. Robust monitoring practices are foundational for operational excellence, supporting reliability and scalability goals in cloud native systems.\\nReal-world example:\\nPrivate health insurance company HanseMerkur, used Calico to reduce infrastructure overhead and meet ISO 27001 compliance standards. The platform\\u2019s unified observability helped the team simplify security operations while gaining visibility into critical workloads across Kubernetes environments.\\nClick here to read the HanseMerkur case study.\\u00a0\\nCloud Native Networking, Security, and Observability with Calico\\nCalico provides a comprehensive set of capabilities purpose-built for cloud native environments, combining scalable networking, fine-grained security controls, and deep observability across Kubernetes clusters. Whether operating in single or multi-cluster environments, Calico empowers platform, security, and DevOps teams to deliver secure, reliable, and high-performance applications at scale.\\nHow Calico Supports Cloud Native Networking\\nHigh-Performance Data Planes\\nCalico supports multiple data planes\\u2014including eBPF, iptables, nftables, and VPP\\u2014enabling teams to choose the best option for performance, compatibility, and operational visibility. The eBPF data plane delivers low latency, high throughput, and efficient resource usage, making it ideal for high-scale production environments.\\nMulti-Cluster and Hybrid Connectivity\\nCalico enables resilient pod-to-pod communication across clusters and supports a wide range of environments including cloud, on-premises, and bare metal. Multi-cluster service connectivity and cluster mesh capabilities ensure seamless workload interoperability and simplified application delivery across diverse infrastructures.\\nIngress and Egress Gateways\\nCalico provides robust ingress and egress gateway capabilities, allowing teams to securely manage external communication. Egress gateways enable fixed, routable IPs for outbound traffic, supporting compliance and firewall configurations. Ingress gateways provide centralized control for managing incoming traffic using standard Kubernetes APIs.\\nHow Calico Supports Network Security in Kubernetes\\nFine-Grained Network Policy Control\\nCalico extends native Kubernetes NetworkPolicy with advanced capabilities such as global policies, policy tiers, and DNS-based rules. Teams can define security policies that span across namespaces or clusters, supporting both L3\\/L4 and application-aware L7 enforcement.\\nMicrosegmentation and Threat Prevention\\nBuilt-in microsegmentation capabilities allow teams to isolate workloads and limit lateral movement, reducing the blast radius of potential attacks. Calico also supports data-in-transit encryption with WireGuard, intrusion detection and prevention (IDS\\/IPS), and protections against DDoS and web application threats.\\nPolicy Lifecycle Management\\nSecurity policies can be staged, previewed, and tested before enforcement, reducing the risk of disruptions. Calico enables a policy-as-code approach that integrates with CI\\/CD pipelines, ensuring security policies are version-controlled and aligned with application delivery workflows.\\nHow Calico Enhances Observability for Cloud Native Operations\\nReal-Time Service and Threat Graphs\\nCalico provides dynamic, interactive visualizations of service-to-service communication, network flows, and policy enforcement. These graphs help teams quickly understand dependencies, identify anomalies, and respond to threats or misconfigurations across workloads and namespaces.\\nDeep Protocol and Application-Level Visibility\\nCalico delivers L7 observability without requiring a full service mesh, offering insight into HTTP traffic patterns, response codes, request latency, and endpoint behavior. DNS dashboards provide workload-aware visibility into DNS activity, making it easier to detect misconfigurations and abnormal query patterns.\\nTargeted Troubleshooting and Root Cause Analysis\\nAdvanced tools such as dynamic packet capture and flow visualizers enable precise, on-demand debugging without disrupting production. These features accelerate incident response by providing direct access to traffic data at the pod or node level.\\nCentralized Monitoring and Compliance Reporting\\nCalico aggregates enriched logs, metrics, and policy data across clusters into unified dashboards. Teams can monitor network behavior, track policy compliance, and export data to external systems for further analysis. Automated compliance reporting supports standards such as PCI DSS, HIPAA, and SOC 2.\\n\\u00a0\\nReal-World Example:\\nBox, a cloud content management and file sharing company, adopted Calico to implement zero-trust security and policy automation at scale across multi-cluster environments. Calico\\u2019s observability capabilities provided Box with real-time visibility into workload communication and policy behaviour, significantly accelerating incident response and simplifying policy troubleshooting across clusters.\\nClick here to read the full case study.\\nNext Steps:\\nEnforcing workload isolation and segmentation in Kubernetes using Calico\\nIntegrating Calico security policies into DevSecOps workflows\\nMonitoring Kubernetes network traffic with Calico dashboards\\nPROJECT CALICO\\nWhat is Project Calico?\\nDocs\\nCommunity\\nGitHub\\nPRODUCTS\\nCalico Open Source\\nCalico Commercial Editions\\nCompare Calico Editions\\nPricing\\nWhy Calico?\\nSOLUTIONS\\nIngress Gateway\\nEgress Gateway\\nCluster Mesh\\nMulti-Cloud Security\\nObservability & Troubleshooting\\nCompliance\\nMicrosegmentation\\nEnvironments\\nLEARN\\nDocumentation\\nInteractive Training\\nProduct Tutorials\\nCertification\\nEvents\\nResources\\nBlog\\nGuides\\nSUPPORT\\nCustomer Success\\nSupport Portal\\nTigera Help Center\\nSecurity Bulletins\\nReport Security Issue\\nCOMPANY\\nAbout\\nCalicoCon 2025\\nCustomers\\nPartners\\nNewsroom\\nCareers\\nContact\\nCopyright \\u00a9\\nTigera, Inc. All rights reserved.\\nPrivacy Center\\nDo Not Sell Or Share My Personal Information\\nLegal\\nLinkedin\\nTwitter\\nYoutube\\nSlack\\nGithub\\nDiscourse\\n\"}"
},
"response": {
"status": "ok",
"response": [
"Right, here's a summary of that lot, in bullet points:",
"•\t**Calico Overview:** Calico provides networking, security, and observability for cloud-native environments like Kubernetes.",
"•\t**Products:** Includes Calico Open Source and commercial editions (Calico Cloud and Calico Enterprise).",
"•\t**Key Features of Cloud Native Applications:**",
"\tâ—‹\tMicroservices architecture (small, independent services).",
"\tâ—‹\tContainer orchestration (e.g., Kubernetes for managing containers).",
"\tâ—‹\tImmutable infrastructure (replacing entire infrastructure with new versions).",
"\tâ—‹\tAutomation (using DevOps and CI/CD practices).",
"\tâ—‹\tResilience (self-healing and automated failover).",
"\tâ—‹\tScalability (easily scale up or down based on demand).",
"\tâ—‹\tPortability (across different cloud providers).",
"•\t**Benefits of Cloud Native:** Faster development, increased agility, improved scalability, reduced costs, and enhanced innovation.",
"•\t**Principles of Cloud Native:**",
"\tâ—‹\tMicroservices architecture.",
"\tâ—‹\tContainerisation.",
"\tâ—‹\tDynamic orchestration.",
"\tâ—‹\tDeclarative APIs.",
"\tâ—‹\tAutomation (DevOps, CI/CD).",
"\tâ—‹\tResilience and observability.",
"\tâ—‹\tScalability and elasticity.",
"\tâ—‹\tPortability.",
"•\t**Pros of Cloud Native:** Scalability, resilience, faster delivery, portability, resource optimisation, and improved collaboration.",
"•\t**Cons of Cloud Native:** Complexity, steep learning curve, increased operational overhead, cost management difficulties, vendor lock-in risks, and security challenges.",
"•\t**Cloud Native vs. Cloud-Based:** Cloud-based applications are often legacy systems moved to the cloud, while cloud native applications are built specifically for the cloud.",
"•\t**Key Use Cases:**",
"\tâ—‹\tDevOps and CI/CD (automating software delivery).",
"\tâ—‹\tLegacy modernisation (migrating old applications to the cloud).",
"\tâ—‹\tService mesh and messaging (managing inter-service communication).",
"\tâ—‹\tMedia and streaming (dynamic scalability for media delivery).",
"•\t**Best Practices for Implementation:**",
"\tâ—‹\tDesign for resilience and failover.",
"\tâ—‹\tImplement DevSecOps (integrate security into DevOps).",
"\tâ—‹\tLeverage cloud load balancers and ingress controllers.",
"\tâ—‹\tUse GitOps practices (manage infrastructure as code).",
"\tâ—‹\tEnsure comprehensive monitoring.",
"•\t**HanseMerkur Case Study:** Used Calico to reduce overhead and meet ISO 27001 compliance.",
"•\t**Calico's Support:**",
"\tâ—‹\tNetworking: High-performance data planes, multi-cluster connectivity, ingress/egress gateways.",
"\tâ—‹\tSecurity: Fine-grained network policy control, microsegmentation, threat prevention, policy lifecycle management.",
"\tâ—‹\tObservability: Real-time service and threat graphs, deep protocol visibility, targeted troubleshooting, centralised monitoring.",
"•\t**Box Case Study:** Adopted Calico for zero-trust security and policy automation across multi-cluster environments.",
"•\t**Next Steps:** Enforcing workload isolation, integrating security policies, monitoring network traffic.",
"•\t**Project Calico:** Includes documentation, community resources, and GitHub repository.",
"•\t**Company Information:** Tigera, Inc. owns Project Calico and provides support, resources and products."
]
}
} {
"prompt": {
"label": "is_firewall",
"prompt": {
"prompt_id": "6",
"prompt_label": "is_firewall",
"content_format": "{\"data\":\"content\"}",
"success_format": "{\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"}",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON.\nIgnore cookie requests in your judgment.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: {\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"} Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON. Ignore cookie requests in your judgment."
},
"content": "{\"data\":\"Downloads\\nContact us\\nClose\\nContact us\\nContact Sales\\nTechnical Support\\nBuy Online\\nLog In\\nClose\\nMy Account\\nVeeam Data Cloud Log In\\nMy Cases\\nSign out\\nVeeam logo\\nMenu\\nMenu\\nProducts\\nProducts\\nVeeam Portfolio\\nFree Community Editions\\nHow To Buy\\nVeeam Portfolio\\nVeeam Data Cloud\\nSaaS Data Protection Solution\\n\\u200b\\nBackup & Recovery service for:\\nMicrosoft 365 & Entra ID\\nMicrosoft Azure\\nSalesforce\\nVault Cloud Storage\\nVeeam Data Platform\\nSelf-managed data protection software for hybrid and multi-cloud environments\\nData Protection\\nCyber Security\\nAI-Driven Insights\\nSovereignty, Governance & Compliance\\nContainers & Modern Virtualization\\nServices\\nCyber Extortion Response\\nCyber Secure Program\\nNEW RELEASE\\nVeeam Data Platform v13\\u00a0\\nSimplify operations and strengthen security with Veeam\\u2019s most intelligent and secure release yet\\u00a0\\nExplore now\\nFree Community Editions\\nHybrid & Multi-Cloud\\nVeeam Backup & Replication CE\\nAll Free Tools\\nCloud\\nVeeam Backup\\nfor AWS\\nFree\\nVeeam Backup\\nfor Microsoft Azure\\nFree\\nVeeam Backup\\nfor Google Cloud\\u00a0\\nFree\\nVeeam Kasten Free\\nSaaS\\nVeeam Backup\\nfor Microsoft 365\\nCE\\nVeeam Insights\\nfor Microsoft 365\\nVeeam\\nfor Salesforce\\nCE\\nHow To Buy\\nVeeam Data Platform\\nSelf-managed data protection software for hybrid and multi-cloud environments\\nPackaging & Enterprise Editions\\nVeeam Data Cloud\\nSaaS Data Resilience Solutions\\nPurchasing Options\\nAll Products\\nFind a Reseller\\nBuy Online\\nSolutions\\nSolutions\\nUse Case\\nRansomware Recovery\\nHybrid Cloud\\nMicrosoft SaaS Data Protection\\nIndustries\\nGovernment\\nEducation\\nFinancial Services & Insurance\\nHealthcare\\nBusiness Type\\nEnterprise\\nSmall Business\\nService Provider\\nServices\\nCyber Extortion Response\\nCyber Secure Program\\nAlliance Technologies\\nSee All Veeam Alliance Partners\\nSee Security Integrations\\nAWS\\nHPE\\nMicrosoft\\nNutanix\\nPure Storage\\nRed Hat\\nAlliance Partner Integrations & Qualifications\\nEnvironment\\nSaaS\\n\\u00a0\\u00a0\\nMicrosoft 365\\n\\u00a0|\\u00a0\\nMicrosoft Entra\\u00a0ID\\n\\u00a0|\\u00a0\\nSalesforce\\nCloud\\u00a0\\n\\u00a0\\nAWS\\n\\u00a0|\\u00a0\\nAzure\\n\\u00a0|\\u00a0\\nGoogle\\n\\u00a0|\\u00a0\\nKubernetes\\nVirtual\\n\\u00a0\\u00a0\\nVMware\\n\\u00a0|\\u00a0\\nHyper-V\\n\\u00a0|\\u00a0\\nNutanix AHV\\n\\u00a0|\\nOracle\\u00a0Linux\\u00a0VM\\n\\u00a0|\\u00a0\\nRHV\\n\\u00a0|\\u00a0\\nProxmox\\n\\u00a0|\\u00a0\\nScale Computing\\nPhysical\\n\\u00a0\\u00a0\\nWindows\\n\\u00a0|\\u00a0\\nLinux\\n\\u00a0|\\u00a0\\nMacOS\\n\\u00a0|\\u00a0\\nUnix\\n\\u00a0|\\u00a0\\nNAS\\nApps\\u00a0\\n\\u00a0\\nMicrosoft\\n\\u00a0|\\u00a0\\nOracle\\n\\u00a0|\\u00a0\\nSAP\\u00a0Hana\\n\\u00a0|\\nPostgreSQL\\n\\u00a0|\\nMongoDB\\nSupport\\nSupport\\nGet Support\\nSupport\\nOpen a Case\\nTrack Your Case\\nSupport Policy\\nRenewals Center\\nRenewals\\nServices\\nVeeam Customer Success\\nTraining & Education\\nVeeam University\\nKubernetes Learning Portal\\nSupport Resources\\nVeeam Data Cloud Changelog\\nTechnical Documentation\\nKnowledge Base\\nKasten Technical Documentation\\nKasten Knowledge Base\\nDownloads\\nAll Product Downloads\\nCommunity\\nCommunity Resource Hub\\nCommunity Experts\\nR&D Forums\\nResources\\nResources\\nThought Leadership\\nData Resilience Maturity Model\\nResource Library\\nWhite Papers\\nSolution Briefs\\nAnalyst Reports\\nSee All Resources\\nCustomer Stories\\nSee All Stories\\nBlog\\nVeeam Blog\\nGlossary\\nVeeam Glossary\\nEvents & Webinars\\nVeeamON\\nEvents\\nUpcoming Webinars\\nOn-Demand Webinars\\nProduct Demo\\nOn-Demand Platform Demo\\nUpcoming Product Demos\\nOn-Demand Product Demos\\nResilience Benchmarking\\nData Resilience Maturity Model\\nPartners\\nPartners\\nWHY PARTNER WITH VEEAM\\nBecome a Partner\\nValue-Added Reseller\\nService Provider\\nGlobal System Integrator\\nTechnology Alliance\\nFind a Partner\\nFind a Partner\\nPartner Resources\\nProPartner Portal\\nCXOs\\nCXOs\\nVeeam\\u2019s exclusive community that brings together a suite of experiences & resources for executive leaders.\\nGain access to:\\nConversations between influential tech leaders\\nMeaningful connection and candid dialogue\\nPeer-to-peer collaborative problem-solving\\nThought Leadership\\u200b\\nbe: Ready\\n- Explore expert guidance, trends, and innovations at our leadership hub online\\u200b\\nINSIGHTS & RESEARCH FOR CXOs\\nExecutive Exchange Events\\u200b\\nNetworking, insights, and shared CXO experiences at exclusive events worldwide\\nEvents for CXOs\\nClose\\nContact us\\nContact Sales\\nTechnical Support\\nClose\\nMy Account\\nVeeam Data Cloud Log In\\nMy Cases\\nSign out\\nTRY NOW\\nbook meeting\\nVeeam Glossary\\nWhat is Cloud Native?\\nWhat is Cloud Native?\\nWhat Is Cloud Native?\\nCloud-Native Architecture\\nBenefits of Embracing Cloud Native\\nChallenges in Cloud-Native Adoption\\nHow to Implement Cloud-Native Practices\\nCloud-Native FAQs\\nExploring the Cloud-Native Ecosystem\\nBecoming Cloud Native With Veeam\\nCloud native is a software development approach that involves building, deploying and managing modern applications in cloud computing environments. Using the practices and technologies of cloud native, you can develop and run scalable, highly available and resilient applications in the cloud. Applications built using cloud native are able to take full advantage of cloud computing resources, such as containers, microservices and orchestration, to optimize resource utilization and improve performance.\\nUnderstanding cloud native is essential if your organization wants to leverage the full potential of the cloud and stay competitive in today's fast-paced digital landscape. By adopting cloud-native practices, your company can accelerate its software delivery, reduce its downtime and improve its customer experience.\\nCloud-Native Architecture\\nCloud native involves a few key concepts that we'll define below.\\n\\u00a0\\nMicroservices\\nMicroservices\\nare separate components that work together to perform as a single cloud-native software solution. Each service focuses on a specific problem, usually something small. They communicate with each other via APIs.\\nContainers and Container Orchestration\\nContainers\\nare a lightweight and portable way to package and deploy software applications. Container orchestration is the automated management of containerized applications, including deployment, scaling and networking, to ensure they run efficiently and reliably in production environments.\\n\\u00a0\\nDevOps Practices\\nDevOps\\npractices in cloud native involve leveraging containerization, automation and orchestration tools to build, test and deploy applications in a continuous integration and continuous delivery pipeline.\\n\\u00a0\\nImmutable Infrastructure\\nImmutable\\ninfrastructure refers to computer infrastructure, such as virtual machines, containers and network appliances, that cannot be changed once deployed. This immutability is self-governing, not allowing changes to be made.\\n\\u00a0\\nScalability and Elasticity\\nScalability in cloud native is the ability of a system to handle an increasing amount of work by adding resources. Elasticity refers to the ability of a system to automatically adjust its resources to meet changing demands in real time.\\n\\u00a0\\nService Mesh\\nA service mesh is an infrastructure layer that manages service-to-service communication within a microservices architecture, providing features such as traffic management, service discovery and security.\\n\\u00a0\\nServerless Computing\\nServerless computing is a cloud computing model where you can run apps without the need to manage the actual infrastructure.\\nCloud-Native Applications\\nCloud-native applications are software applications that are designed, developed and deployed in the cloud using technologies and services that are also based in the cloud.\\nBenefits of Embracing Cloud Native\\nYou may want to consider cloud native for your organization because it offers a host of benefits. Here are five major ones.\\n\\u00a0\\nAgility and Faster Time to Market\\nEmbracing cloud native allows for a more agile development environment, meaning your company can bring its technology to market faster. Because cloud-native technology optimizes the cloud's capabilities, your organization can more easily build application portfolios that keep up with the changing demands of the market.\\nCloud-native development supported by DevOps processes and automation results in accelerated software delivery, as opposed to local or server-based development and the limitations that come with that. This faster marketing time helps your company respond to rapidly changing demands and market conditions.\\n\\u00a0\\nCost Efficiency\\nCloud-native architectures reduce operational complexity, simplify configuration changes and are extremely reliable. When your organization adopts the cloud-native approach, it doesn't have to invest in costly physical infrastructure. This results in major savings in operating costs in the long run.\\n\\u00a0\\nImproved Scalability and Resilience\\nCloud-native architecture allows your developers to build, run and update software through multiple independent microservices. This makes it easier to scale up or down as needed and results in faster release cycles, reduced development costs and automated recovery and backup.\\n\\u00a0\\nEnhanced Collaboration and Developer Productivity\\nEmbracing cloud native can make your developers more productive and help them collaborate seamlessly, by enabling them to communicate more closely and come together around a shared purpose. This helps create an environment where applications can be built, tested and released faster.\\nCloud-native tools and services are designed for the unique demands of cloud-based environments, helping developers build, deploy and manage their applications more efficiently, ultimately improving productivity.\\n\\u00a0\\nSecurity and Compliance Advantages\\nCloud-native security offers improved visibility and monitoring, and security is provided as a completely managed service, which means your organization doesn't need to dedicate its own resources. Cloud native also keeps your team compliant with laws and regulations that apply to the adoption of cloud infrastructures. With cloud native, there's no need for on-premise hardware, which saves you from having to dedicate space, power and other resources to secure your technology.\\n\\u00a0\\nChallenges in Cloud-Native Adoption\\nWhile the benefits of adopting cloud native are significant, the process can also pose a few challenges that you and your team should be aware of.\\n\\u00a0\\nCultural Shifts\\nCultural shifts can present a challenge when it comes to embracing cloud native. The shift toward a cloud-native mindset may require you to adjust your organizational culture into one that promotes collaboration, flexibility and scalability in both work processes and technology. This is because cloud-native computing is not always easy or straightforward to implement, especially if your company is used to working with legacy applications. The cloud-native landscape is vast, and it's easy to become overwhelmed by its growing number of competing and overlapping platforms and technologies.\\n\\u00a0\\nTechnical Complexity\\nCloud-native applications are built using microservices, containers and orchestration tools. These tools can be complex to manage, and this might become overwhelming if your organization lacks the expertise and resources to manage them.\\n\\u00a0\\nSecurity Concerns\\nSecurity concerns\\nare another potential challenge when it comes to embracing cloud native. The cyber threats to cloud-based applications are diverse and often significant. The fact that your applications are no longer local and always visible might also pose a challenge. Traditional security measures often have difficulty matching the scale of today's cloud-native architectures. Rather than trying to upgrade your physical security, consider cloud-based solutions such as\\nBackup as a Service\\n.\\n\\u00a0\\nVendor Lock-In\\nVendor lock-in is a situation where you become dependent on a single cloud provider technology implementation and cannot easily move to a different vendor without substantial costs, legal constraints or technical incompatibilities. This can keep your apps from being portable and interoperable. Because cloud providers offer different operating systems, databases and security tools, it can be difficult to switch to another provider or solution.\\n\\u00a0\\nMonitoring and Observability\\nCloud-native\\napplications are built using microservices, which create many interdependencies. This complexity might make it difficult to monitor and observe the system.\\n\\u00a0\\nHow to Implement Cloud-Native Practices\\nIf you're ready to implement cloud-native practices into your organization's technology stack, here are the steps to follow.\\n\\u00a0\\nAssessing Your Current State\\nAssessing your current state is the first step in implementing cloud-native practices. This involves evaluating your existing infrastructure, applications and processes to identify areas that can be improved by adopting cloud-native practices. By assessing your current state, you can identify the gaps between where you are now and where you want to be. This will help you develop a roadmap for implementing cloud-native practices.\\n\\u00a0\\nDeveloping a Cloud-Native Strategy\\nDeveloping a cloud-native strategy is the next step. This allows you to define how you'll meet specific objectives within your organization by harnessing cloud infrastructure and tools such as containers. It's important to understand the tie between cloud-native and container-based applications and DevOps.\\n\\u00a0\\nTooling and Infrastructure\\nNext, you'll need to understand how to use the right tools and techniques that support application development on cloud infrastructure. This includes containerization, orchestration tools and microservice architecture.\\n\\u00a0\\nBest Practices and Patterns\\nHere are a few best practices to keep in mind when implementing cloud native:\\n\\u00a0\\nTake advantage of microservices.\\nUse lightweight containers whenever possible.\\nUse the right languages and frameworks.\\nAutomate your release pipeline with continuous integration and continuous delivery.\\nAvoid vendor lock-in.\\nIntegrate robust security from the start.\\nCase Studies and Success Stories\\nIn 2023, a\\ncloud-native case study\\nwas released via LinkedIn, detailing success stories from organizations that have implemented cloud native.\\nCloud-Native FAQs\\nIt's common to have questions when considering a major technological overhaul such as implementing cloud native. Here are a few of the most commonly asked questions by people who are new to the process.\\u00a0\\nWhat is Cloud Native vs. Cloud?\\nCloud and cloud native sound similar, but they have some important differences. Cloud refers to the use of remote servers to store, manage and process data. Cloud native refers specifically to applications that are designed and built to be used in a cloud environment.\\nCloud-based applications that aren't cloud-native can be deployed on the cloud, but they may not be optimized for the cloud environment. They might also require physical infrastructure to run.\\nCloud-native applications are built and deployed in the cloud, and they take full advantage of the cloud's benefits when it comes to flexibility, scalability and security. They are designed only to run on the cloud and are thus optimized for cloud performance.\\n\\u00a0\\nWhat is Cloud Native vs. Cloud Agnostic?\\nCloud native and cloud agnostic both refer to applications built specifically to run on the cloud. Cloud-native applications, however, are built to run on a specific cloud platform that offers a specific toolkit. They're optimized for performance and scalability on that specific platform.\\nCloud-agnostic applications, in contrast, are designed to run on any\\ncloud platform\\n, without being tied to any specific cloud provider. They offer more flexibility and portability but typically aren't optimized for specific cloud services. Cloud-agnostic applications can incorporate open-source tools and integrations that are constantly evolving to reflect emerging development trends.\\n\\u00a0\\nWhat is Cloud Native vs. SaaS?\\nCloud native and SaaS are two different approaches to running applications on the cloud. With cloud native, your organization runs its own applications that are specifically designed for use on the cloud. With SaaS, you pay a subscription for the use of third-party applications that exist on the cloud.\\n\\u00a0\\nExploring the Cloud-Native Ecosystem\\nThe cloud-native ecosystem is vast, and the learning curve to understanding all its ins and outs can be steep. We recommend starting by knowing who some of the big providers are in the cloud-native space, as well as the popular cloud-native tools and frameworks.\\nThere's also a large cloud-native community online that can help you along the way and point you to the best resources for any issue you're facing.\\u00a0\\nCloud Providers in the Cloud-Native Space\\nA few of the most well-known and reputable cloud providers in the cloud-native space include the following:\\n\\u00a0\\nAmazon Web Services\\nMicrosoft Azure\\nGoogle Cloud Platform\\nAlibaba Cloud\\nOracle Cloud\\nIBM Cloud\\nDigitalOcean\\nLinode\\nOVHcloud\\nTencent Cloud\\nPopular Cloud-Native Tools and Frameworks\\nSome of the most-used tools and frameworks in the cloud-native sphere include:\\n\\u00a0\\nDocker:\\nA platform that allows you to build and run distributed applications in containers\\nKubernetes\\n:\\nAn open-source for deploying and managing containerized applications\\nPrometheus:\\nA toolkit for monitoring cloud-native systems\\nEnvoy:\\nA proxy for load balancing, routing and observing microservices\\nYou can also refer to\\nCloud Native Computing Foundation\\nand\\nThe New Stack\\nto learn more about cloud native.\\n\\u00a0\\nBecoming Cloud Native With Veeam\\nImplementing cloud native offers an array of benefits, including agility, scalability, cost-efficiency and time to market, among other things. However, you should be aware of some potential challenges, such as security concerns, technical complexities and cultural compatibility. In the end, implementing cloud native will pay off for your organization as long as you're diligent about following the steps to a successful implementation.\\nThe first step is to explore further by learning about\\nVeeam's cloud solutions\\nand contacting one of our cloud experts today. We can help your organization protect, control and manage your data anywhere.\\n\\u00a0\\nRelated Content\\nWhat is Multi-Cloud?\\nBenefits of Hyper-V Virtualization\\nBaaS for Public Cloud: Cloud-native data protection, managed for you!\\nHow to Back Up VMware VMs\\nNEW Cloud Backup Options With Veeam Agents\\nSaving Time With Virtualization\\nWhat is Container Security?\\nVM Glossary Page\\nHypervisor Glossary Page\\nConnect With Us\\n1-800-691-1991\\nSubscribe to our product news\\nVeeam\\nAbout\\nLeadership\\nCareers\\nCorporate Governance\\nContact Us\\nPress Releases\\nBrand Resource Center\\nTrust Center\\nSupport\\nSupport\\nTechnical Documentation\\nCustomer Success\\nRenewals\\nVeeam University\\nVeeam Data Cloud Change Log\\nCommunity Resource Hub\\nR&D Forum\\nProducts & Solutions\\nVeeam Portfolio\\nVeeam Data Platform\\nVeeam Data Cloud\\nSecure Cloud Storage\\nData Protection\\nCyber Security\\nAI Driven Insights\\nSovereignty, Governance & Compliance\\nSalesforce\\nKubernetes\\nMicrosoft 365 & Entra ID\\nBackup & Replication\\nResources\\nInsights & Research For CXOs\\nEvents For CXOs\\nResource Library\\nWhite Papers\\nOn-Demand Webinars\\nCustomer Stories\\nOn-Demand Product Demos\\nChange language\\nPlease select a language\\nEnglish\\nDeutsch\\nEspa\\u00f1ol\\nFran\\u00e7ais\\nItaliano\\nNederlands\\nPolski\\nPortugu\\u00eas\\nT\\u00fcrk\\u00e7e\\n\\u65e5\\u672c\\u8a9e\\n\\u4e2d\\u6587\\uff08\\u7b80\\u4f53\\uff09\\n\\ud55c\\uad6d\\uc5b4\\n\\u00a92026 Veeam\\u00ae Software\\n|\\nPrivacy Notice\\n|\\nCookie Notice\\n|\\nLegal\\n|\\nLicensing Policy\\n|\\nSupplier Resources\\n\"}"
},
"response": {
"status": "false",
"response": "false"
}
} {
"prompt": {
"label": "resume_data",
"prompt": {
"prompt_id": "7",
"prompt_label": "resume_data",
"content_format": "{\"data\":\"content\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you."
},
"content": "{\"data\":\"Downloads\\nContact us\\nClose\\nContact us\\nContact Sales\\nTechnical Support\\nBuy Online\\nLog In\\nClose\\nMy Account\\nVeeam Data Cloud Log In\\nMy Cases\\nSign out\\nVeeam logo\\nMenu\\nMenu\\nProducts\\nProducts\\nVeeam Portfolio\\nFree Community Editions\\nHow To Buy\\nVeeam Portfolio\\nVeeam Data Cloud\\nSaaS Data Protection Solution\\n\\u200b\\nBackup & Recovery service for:\\nMicrosoft 365 & Entra ID\\nMicrosoft Azure\\nSalesforce\\nVault Cloud Storage\\nVeeam Data Platform\\nSelf-managed data protection software for hybrid and multi-cloud environments\\nData Protection\\nCyber Security\\nAI-Driven Insights\\nSovereignty, Governance & Compliance\\nContainers & Modern Virtualization\\nServices\\nCyber Extortion Response\\nCyber Secure Program\\nNEW RELEASE\\nVeeam Data Platform v13\\u00a0\\nSimplify operations and strengthen security with Veeam\\u2019s most intelligent and secure release yet\\u00a0\\nExplore now\\nFree Community Editions\\nHybrid & Multi-Cloud\\nVeeam Backup & Replication CE\\nAll Free Tools\\nCloud\\nVeeam Backup\\nfor AWS\\nFree\\nVeeam Backup\\nfor Microsoft Azure\\nFree\\nVeeam Backup\\nfor Google Cloud\\u00a0\\nFree\\nVeeam Kasten Free\\nSaaS\\nVeeam Backup\\nfor Microsoft 365\\nCE\\nVeeam Insights\\nfor Microsoft 365\\nVeeam\\nfor Salesforce\\nCE\\nHow To Buy\\nVeeam Data Platform\\nSelf-managed data protection software for hybrid and multi-cloud environments\\nPackaging & Enterprise Editions\\nVeeam Data Cloud\\nSaaS Data Resilience Solutions\\nPurchasing Options\\nAll Products\\nFind a Reseller\\nBuy Online\\nSolutions\\nSolutions\\nUse Case\\nRansomware Recovery\\nHybrid Cloud\\nMicrosoft SaaS Data Protection\\nIndustries\\nGovernment\\nEducation\\nFinancial Services & Insurance\\nHealthcare\\nBusiness Type\\nEnterprise\\nSmall Business\\nService Provider\\nServices\\nCyber Extortion Response\\nCyber Secure Program\\nAlliance Technologies\\nSee All Veeam Alliance Partners\\nSee Security Integrations\\nAWS\\nHPE\\nMicrosoft\\nNutanix\\nPure Storage\\nRed Hat\\nAlliance Partner Integrations & Qualifications\\nEnvironment\\nSaaS\\n\\u00a0\\u00a0\\nMicrosoft 365\\n\\u00a0|\\u00a0\\nMicrosoft Entra\\u00a0ID\\n\\u00a0|\\u00a0\\nSalesforce\\nCloud\\u00a0\\n\\u00a0\\nAWS\\n\\u00a0|\\u00a0\\nAzure\\n\\u00a0|\\u00a0\\nGoogle\\n\\u00a0|\\u00a0\\nKubernetes\\nVirtual\\n\\u00a0\\u00a0\\nVMware\\n\\u00a0|\\u00a0\\nHyper-V\\n\\u00a0|\\u00a0\\nNutanix AHV\\n\\u00a0|\\nOracle\\u00a0Linux\\u00a0VM\\n\\u00a0|\\u00a0\\nRHV\\n\\u00a0|\\u00a0\\nProxmox\\n\\u00a0|\\u00a0\\nScale Computing\\nPhysical\\n\\u00a0\\u00a0\\nWindows\\n\\u00a0|\\u00a0\\nLinux\\n\\u00a0|\\u00a0\\nMacOS\\n\\u00a0|\\u00a0\\nUnix\\n\\u00a0|\\u00a0\\nNAS\\nApps\\u00a0\\n\\u00a0\\nMicrosoft\\n\\u00a0|\\u00a0\\nOracle\\n\\u00a0|\\u00a0\\nSAP\\u00a0Hana\\n\\u00a0|\\nPostgreSQL\\n\\u00a0|\\nMongoDB\\nSupport\\nSupport\\nGet Support\\nSupport\\nOpen a Case\\nTrack Your Case\\nSupport Policy\\nRenewals Center\\nRenewals\\nServices\\nVeeam Customer Success\\nTraining & Education\\nVeeam University\\nKubernetes Learning Portal\\nSupport Resources\\nVeeam Data Cloud Changelog\\nTechnical Documentation\\nKnowledge Base\\nKasten Technical Documentation\\nKasten Knowledge Base\\nDownloads\\nAll Product Downloads\\nCommunity\\nCommunity Resource Hub\\nCommunity Experts\\nR&D Forums\\nResources\\nResources\\nThought Leadership\\nData Resilience Maturity Model\\nResource Library\\nWhite Papers\\nSolution Briefs\\nAnalyst Reports\\nSee All Resources\\nCustomer Stories\\nSee All Stories\\nBlog\\nVeeam Blog\\nGlossary\\nVeeam Glossary\\nEvents & Webinars\\nVeeamON\\nEvents\\nUpcoming Webinars\\nOn-Demand Webinars\\nProduct Demo\\nOn-Demand Platform Demo\\nUpcoming Product Demos\\nOn-Demand Product Demos\\nResilience Benchmarking\\nData Resilience Maturity Model\\nPartners\\nPartners\\nWHY PARTNER WITH VEEAM\\nBecome a Partner\\nValue-Added Reseller\\nService Provider\\nGlobal System Integrator\\nTechnology Alliance\\nFind a Partner\\nFind a Partner\\nPartner Resources\\nProPartner Portal\\nCXOs\\nCXOs\\nVeeam\\u2019s exclusive community that brings together a suite of experiences & resources for executive leaders.\\nGain access to:\\nConversations between influential tech leaders\\nMeaningful connection and candid dialogue\\nPeer-to-peer collaborative problem-solving\\nThought Leadership\\u200b\\nbe: Ready\\n- Explore expert guidance, trends, and innovations at our leadership hub online\\u200b\\nINSIGHTS & RESEARCH FOR CXOs\\nExecutive Exchange Events\\u200b\\nNetworking, insights, and shared CXO experiences at exclusive events worldwide\\nEvents for CXOs\\nClose\\nContact us\\nContact Sales\\nTechnical Support\\nClose\\nMy Account\\nVeeam Data Cloud Log In\\nMy Cases\\nSign out\\nTRY NOW\\nbook meeting\\nVeeam Glossary\\nWhat is Cloud Native?\\nWhat is Cloud Native?\\nWhat Is Cloud Native?\\nCloud-Native Architecture\\nBenefits of Embracing Cloud Native\\nChallenges in Cloud-Native Adoption\\nHow to Implement Cloud-Native Practices\\nCloud-Native FAQs\\nExploring the Cloud-Native Ecosystem\\nBecoming Cloud Native With Veeam\\nCloud native is a software development approach that involves building, deploying and managing modern applications in cloud computing environments. Using the practices and technologies of cloud native, you can develop and run scalable, highly available and resilient applications in the cloud. Applications built using cloud native are able to take full advantage of cloud computing resources, such as containers, microservices and orchestration, to optimize resource utilization and improve performance.\\nUnderstanding cloud native is essential if your organization wants to leverage the full potential of the cloud and stay competitive in today's fast-paced digital landscape. By adopting cloud-native practices, your company can accelerate its software delivery, reduce its downtime and improve its customer experience.\\nCloud-Native Architecture\\nCloud native involves a few key concepts that we'll define below.\\n\\u00a0\\nMicroservices\\nMicroservices\\nare separate components that work together to perform as a single cloud-native software solution. Each service focuses on a specific problem, usually something small. They communicate with each other via APIs.\\nContainers and Container Orchestration\\nContainers\\nare a lightweight and portable way to package and deploy software applications. Container orchestration is the automated management of containerized applications, including deployment, scaling and networking, to ensure they run efficiently and reliably in production environments.\\n\\u00a0\\nDevOps Practices\\nDevOps\\npractices in cloud native involve leveraging containerization, automation and orchestration tools to build, test and deploy applications in a continuous integration and continuous delivery pipeline.\\n\\u00a0\\nImmutable Infrastructure\\nImmutable\\ninfrastructure refers to computer infrastructure, such as virtual machines, containers and network appliances, that cannot be changed once deployed. This immutability is self-governing, not allowing changes to be made.\\n\\u00a0\\nScalability and Elasticity\\nScalability in cloud native is the ability of a system to handle an increasing amount of work by adding resources. Elasticity refers to the ability of a system to automatically adjust its resources to meet changing demands in real time.\\n\\u00a0\\nService Mesh\\nA service mesh is an infrastructure layer that manages service-to-service communication within a microservices architecture, providing features such as traffic management, service discovery and security.\\n\\u00a0\\nServerless Computing\\nServerless computing is a cloud computing model where you can run apps without the need to manage the actual infrastructure.\\nCloud-Native Applications\\nCloud-native applications are software applications that are designed, developed and deployed in the cloud using technologies and services that are also based in the cloud.\\nBenefits of Embracing Cloud Native\\nYou may want to consider cloud native for your organization because it offers a host of benefits. Here are five major ones.\\n\\u00a0\\nAgility and Faster Time to Market\\nEmbracing cloud native allows for a more agile development environment, meaning your company can bring its technology to market faster. Because cloud-native technology optimizes the cloud's capabilities, your organization can more easily build application portfolios that keep up with the changing demands of the market.\\nCloud-native development supported by DevOps processes and automation results in accelerated software delivery, as opposed to local or server-based development and the limitations that come with that. This faster marketing time helps your company respond to rapidly changing demands and market conditions.\\n\\u00a0\\nCost Efficiency\\nCloud-native architectures reduce operational complexity, simplify configuration changes and are extremely reliable. When your organization adopts the cloud-native approach, it doesn't have to invest in costly physical infrastructure. This results in major savings in operating costs in the long run.\\n\\u00a0\\nImproved Scalability and Resilience\\nCloud-native architecture allows your developers to build, run and update software through multiple independent microservices. This makes it easier to scale up or down as needed and results in faster release cycles, reduced development costs and automated recovery and backup.\\n\\u00a0\\nEnhanced Collaboration and Developer Productivity\\nEmbracing cloud native can make your developers more productive and help them collaborate seamlessly, by enabling them to communicate more closely and come together around a shared purpose. This helps create an environment where applications can be built, tested and released faster.\\nCloud-native tools and services are designed for the unique demands of cloud-based environments, helping developers build, deploy and manage their applications more efficiently, ultimately improving productivity.\\n\\u00a0\\nSecurity and Compliance Advantages\\nCloud-native security offers improved visibility and monitoring, and security is provided as a completely managed service, which means your organization doesn't need to dedicate its own resources. Cloud native also keeps your team compliant with laws and regulations that apply to the adoption of cloud infrastructures. With cloud native, there's no need for on-premise hardware, which saves you from having to dedicate space, power and other resources to secure your technology.\\n\\u00a0\\nChallenges in Cloud-Native Adoption\\nWhile the benefits of adopting cloud native are significant, the process can also pose a few challenges that you and your team should be aware of.\\n\\u00a0\\nCultural Shifts\\nCultural shifts can present a challenge when it comes to embracing cloud native. The shift toward a cloud-native mindset may require you to adjust your organizational culture into one that promotes collaboration, flexibility and scalability in both work processes and technology. This is because cloud-native computing is not always easy or straightforward to implement, especially if your company is used to working with legacy applications. The cloud-native landscape is vast, and it's easy to become overwhelmed by its growing number of competing and overlapping platforms and technologies.\\n\\u00a0\\nTechnical Complexity\\nCloud-native applications are built using microservices, containers and orchestration tools. These tools can be complex to manage, and this might become overwhelming if your organization lacks the expertise and resources to manage them.\\n\\u00a0\\nSecurity Concerns\\nSecurity concerns\\nare another potential challenge when it comes to embracing cloud native. The cyber threats to cloud-based applications are diverse and often significant. The fact that your applications are no longer local and always visible might also pose a challenge. Traditional security measures often have difficulty matching the scale of today's cloud-native architectures. Rather than trying to upgrade your physical security, consider cloud-based solutions such as\\nBackup as a Service\\n.\\n\\u00a0\\nVendor Lock-In\\nVendor lock-in is a situation where you become dependent on a single cloud provider technology implementation and cannot easily move to a different vendor without substantial costs, legal constraints or technical incompatibilities. This can keep your apps from being portable and interoperable. Because cloud providers offer different operating systems, databases and security tools, it can be difficult to switch to another provider or solution.\\n\\u00a0\\nMonitoring and Observability\\nCloud-native\\napplications are built using microservices, which create many interdependencies. This complexity might make it difficult to monitor and observe the system.\\n\\u00a0\\nHow to Implement Cloud-Native Practices\\nIf you're ready to implement cloud-native practices into your organization's technology stack, here are the steps to follow.\\n\\u00a0\\nAssessing Your Current State\\nAssessing your current state is the first step in implementing cloud-native practices. This involves evaluating your existing infrastructure, applications and processes to identify areas that can be improved by adopting cloud-native practices. By assessing your current state, you can identify the gaps between where you are now and where you want to be. This will help you develop a roadmap for implementing cloud-native practices.\\n\\u00a0\\nDeveloping a Cloud-Native Strategy\\nDeveloping a cloud-native strategy is the next step. This allows you to define how you'll meet specific objectives within your organization by harnessing cloud infrastructure and tools such as containers. It's important to understand the tie between cloud-native and container-based applications and DevOps.\\n\\u00a0\\nTooling and Infrastructure\\nNext, you'll need to understand how to use the right tools and techniques that support application development on cloud infrastructure. This includes containerization, orchestration tools and microservice architecture.\\n\\u00a0\\nBest Practices and Patterns\\nHere are a few best practices to keep in mind when implementing cloud native:\\n\\u00a0\\nTake advantage of microservices.\\nUse lightweight containers whenever possible.\\nUse the right languages and frameworks.\\nAutomate your release pipeline with continuous integration and continuous delivery.\\nAvoid vendor lock-in.\\nIntegrate robust security from the start.\\nCase Studies and Success Stories\\nIn 2023, a\\ncloud-native case study\\nwas released via LinkedIn, detailing success stories from organizations that have implemented cloud native.\\nCloud-Native FAQs\\nIt's common to have questions when considering a major technological overhaul such as implementing cloud native. Here are a few of the most commonly asked questions by people who are new to the process.\\u00a0\\nWhat is Cloud Native vs. Cloud?\\nCloud and cloud native sound similar, but they have some important differences. Cloud refers to the use of remote servers to store, manage and process data. Cloud native refers specifically to applications that are designed and built to be used in a cloud environment.\\nCloud-based applications that aren't cloud-native can be deployed on the cloud, but they may not be optimized for the cloud environment. They might also require physical infrastructure to run.\\nCloud-native applications are built and deployed in the cloud, and they take full advantage of the cloud's benefits when it comes to flexibility, scalability and security. They are designed only to run on the cloud and are thus optimized for cloud performance.\\n\\u00a0\\nWhat is Cloud Native vs. Cloud Agnostic?\\nCloud native and cloud agnostic both refer to applications built specifically to run on the cloud. Cloud-native applications, however, are built to run on a specific cloud platform that offers a specific toolkit. They're optimized for performance and scalability on that specific platform.\\nCloud-agnostic applications, in contrast, are designed to run on any\\ncloud platform\\n, without being tied to any specific cloud provider. They offer more flexibility and portability but typically aren't optimized for specific cloud services. Cloud-agnostic applications can incorporate open-source tools and integrations that are constantly evolving to reflect emerging development trends.\\n\\u00a0\\nWhat is Cloud Native vs. SaaS?\\nCloud native and SaaS are two different approaches to running applications on the cloud. With cloud native, your organization runs its own applications that are specifically designed for use on the cloud. With SaaS, you pay a subscription for the use of third-party applications that exist on the cloud.\\n\\u00a0\\nExploring the Cloud-Native Ecosystem\\nThe cloud-native ecosystem is vast, and the learning curve to understanding all its ins and outs can be steep. We recommend starting by knowing who some of the big providers are in the cloud-native space, as well as the popular cloud-native tools and frameworks.\\nThere's also a large cloud-native community online that can help you along the way and point you to the best resources for any issue you're facing.\\u00a0\\nCloud Providers in the Cloud-Native Space\\nA few of the most well-known and reputable cloud providers in the cloud-native space include the following:\\n\\u00a0\\nAmazon Web Services\\nMicrosoft Azure\\nGoogle Cloud Platform\\nAlibaba Cloud\\nOracle Cloud\\nIBM Cloud\\nDigitalOcean\\nLinode\\nOVHcloud\\nTencent Cloud\\nPopular Cloud-Native Tools and Frameworks\\nSome of the most-used tools and frameworks in the cloud-native sphere include:\\n\\u00a0\\nDocker:\\nA platform that allows you to build and run distributed applications in containers\\nKubernetes\\n:\\nAn open-source for deploying and managing containerized applications\\nPrometheus:\\nA toolkit for monitoring cloud-native systems\\nEnvoy:\\nA proxy for load balancing, routing and observing microservices\\nYou can also refer to\\nCloud Native Computing Foundation\\nand\\nThe New Stack\\nto learn more about cloud native.\\n\\u00a0\\nBecoming Cloud Native With Veeam\\nImplementing cloud native offers an array of benefits, including agility, scalability, cost-efficiency and time to market, among other things. However, you should be aware of some potential challenges, such as security concerns, technical complexities and cultural compatibility. In the end, implementing cloud native will pay off for your organization as long as you're diligent about following the steps to a successful implementation.\\nThe first step is to explore further by learning about\\nVeeam's cloud solutions\\nand contacting one of our cloud experts today. We can help your organization protect, control and manage your data anywhere.\\n\\u00a0\\nRelated Content\\nWhat is Multi-Cloud?\\nBenefits of Hyper-V Virtualization\\nBaaS for Public Cloud: Cloud-native data protection, managed for you!\\nHow to Back Up VMware VMs\\nNEW Cloud Backup Options With Veeam Agents\\nSaving Time With Virtualization\\nWhat is Container Security?\\nVM Glossary Page\\nHypervisor Glossary Page\\nConnect With Us\\n1-800-691-1991\\nSubscribe to our product news\\nVeeam\\nAbout\\nLeadership\\nCareers\\nCorporate Governance\\nContact Us\\nPress Releases\\nBrand Resource Center\\nTrust Center\\nSupport\\nSupport\\nTechnical Documentation\\nCustomer Success\\nRenewals\\nVeeam University\\nVeeam Data Cloud Change Log\\nCommunity Resource Hub\\nR&D Forum\\nProducts & Solutions\\nVeeam Portfolio\\nVeeam Data Platform\\nVeeam Data Cloud\\nSecure Cloud Storage\\nData Protection\\nCyber Security\\nAI Driven Insights\\nSovereignty, Governance & Compliance\\nSalesforce\\nKubernetes\\nMicrosoft 365 & Entra ID\\nBackup & Replication\\nResources\\nInsights & Research For CXOs\\nEvents For CXOs\\nResource Library\\nWhite Papers\\nOn-Demand Webinars\\nCustomer Stories\\nOn-Demand Product Demos\\nChange language\\nPlease select a language\\nEnglish\\nDeutsch\\nEspa\\u00f1ol\\nFran\\u00e7ais\\nItaliano\\nNederlands\\nPolski\\nPortugu\\u00eas\\nT\\u00fcrk\\u00e7e\\n\\u65e5\\u672c\\u8a9e\\n\\u4e2d\\u6587\\uff08\\u7b80\\u4f53\\uff09\\n\\ud55c\\uad6d\\uc5b4\\n\\u00a92026 Veeam\\u00ae Software\\n|\\nPrivacy Notice\\n|\\nCookie Notice\\n|\\nLegal\\n|\\nLicensing Policy\\n|\\nSupplier Resources\\n\"}"
},
"response": {
"status": "ok",
"response": [
"Veeam offers data protection and cloud solutions.",
"**Cloud Native:**",
" * It's a software development approach for building applications in cloud environments.",
" * It uses containers, microservices, and orchestration.",
" * It helps with scalability and resilience.",
"**Key Concepts of Cloud Native Architecture**",
" * Microservices: Individual components communicating via APIs.",
" * Containers: Lightweight packages for deploying software.",
" * DevOps: Automating building, testing, and deployment.",
" * Immutable Infrastructure: Infrastructure that cannot be changed after being deployed.",
" * Scalability and Elasticity: Ability to handle increasing work and adjust resources.",
" * Service Mesh: Manages service-to-service communication.",
" * Serverless Computing: Run apps without infrastructure management.",
"**Benefits of Cloud Native:**",
" * Faster time to market and agility.",
" * Cost efficiency.",
" * Better scalability and resilience.",
" * Improved developer productivity and collaboration.",
" * Security and compliance.",
"**Challenges of Cloud Native:**",
" * Cultural shifts required.",
" * Technical complexity.",
" * Security concerns.",
" * Vendor lock-in.",
" * Monitoring and observability difficulties.",
"**How to Implement Cloud Native:**",
" * Assess your current state.",
" * Develop a strategy.",
" * Use the right tools and infrastructure.",
" * Follow best practices (e.g., use microservices, containers, automate releases).",
"**Cloud Native vs. Cloud:**",
" * Cloud refers to remote servers for data.",
" * Cloud native refers to applications designed for cloud environments.",
"**Cloud Native vs. Cloud Agnostic:**",
" * Cloud Native apps are built for a specific cloud platform",
" * Cloud Agnostic apps can run on any cloud platform.",
"**Cloud Native vs. SaaS:**",
" * Cloud native involves running your own cloud-designed applications.",
" * SaaS means using third-party applications on the cloud for a subscription fee.",
"**Cloud Providers:**",
" * Amazon Web Services, Microsoft Azure, Google Cloud Platform, etc.",
"**Popular Tools/Frameworks:**",
" * Docker, Kubernetes, Prometheus, Envoy.",
"Contact Veeam for cloud solutions."
]
}
} {
"prompt": {
"label": "is_firewall",
"prompt": {
"prompt_id": "6",
"prompt_label": "is_firewall",
"content_format": "{\"data\":\"content\"}",
"success_format": "{\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"}",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON.\nIgnore cookie requests in your judgment.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: {\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"} Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON. Ignore cookie requests in your judgment."
},
"content": "{\"data\":\"Support\\nServices\\nContact Us\\nEnglish\\nDeutschland (Deutsch)\\nEspa\\u00f1a (Espa\\u00f1ol)\\nFrance (Fran\\u00e7ais)\\nItalia (Italiano)\\nEnglish\\n\\u65e5\\u672c (\\u65e5\\u672c\\u8a9e)\\n\\ub300\\ud55c\\ubbfc\\uad6d(KR)\\nLatinoam\\u00e9rica (Espa\\u00f1ol)\\nBrasil (Portugu\\u00eas)\\n\\u53f0\\u7063 (\\u7e41\\u9ad4\\u4e2d\\u6587)\\nUnited Kingdom (English)\\nAustralia (English)\\nAsia Pacific (English)\\nGo to Section\\nWhat We Do\\nProducts\\nProducts\\nNutanix Cloud Platform\\nNutanix Central\\nNutanix Central\\nPrism\\nNutanix Cloud Infrastructure\\nNutanix Cloud Infrastructure\\nAOS Storage\\nAHV Virtualization\\nNutanix Disaster Recovery\\nFlow Network Security\\nFlow Virtual Networking\\nNutanix Cloud Clusters (NC2)\\nNutanix Government Cloud Clusters (GC2)\\nNCI with External Storage\\nNutanix Database Service\\nNutanix Kubernetes\\u00ae Platform\\nNutanix Kubernetes\\u00ae Platform\\nNutanix Data Services for Kubernetes\\nCloud Native AOS\\nMulticloud Kubernetes\\nNutanix Cloud Manager\\nNutanix Cloud Manager\\nIntelligent Operations\\nSelf-Service\\nCost Governance\\nSecurity Central\\nNutanix Unified Storage\\nNutanix Unified Storage\\nFiles Storage\\nObjects Storage\\nVolumes Block Storage\\nNutanix Data Lens\\nNutanix Enterprise AI\\nFor Deployment Success\\nNutanix Move\\nHardware Platforms\\nSoftware Options\\nCommunity Edition\\nSizer Configuration Estimator\\nX-Ray Performance & Reliability Tests\\nLCM Full-stack Update Manager\\nInsights Support Automation\\nA Leader in the 2025 Gartner\\u00ae Magic Quadrant\\u2122 for Distributed Hybrid Infrastructure\\nSee Why\\nSolutions\\nSolutions\\nKey Solutions\\nVMware Alternative\\nHybrid Cloud Adoption\\nKubernetes Platform\\nCloud\\nBusiness Continuity & Disaster Recovery\\nBusiness-Critical Apps\\nCloud Native\\nDigital Sovereignty\\nEdge (& ROBO)\\nHybrid Multicloud\\nMigrate Applications to Cloud\\nPrivate Cloud\\nSecurity\\nSustainability & IT\\nDatabases\\nDatabase-as-a-Service\\nEnd-User Computing (VDI and DaaS)\\nCitrix\\nEnd-User Computing\\nApplications\\nAI \\/ ML\\nIndustry Solutions\\nAutomotive\\nFinancial Services\\nGovernment and Education\\nHealthcare\\nLegal\\nManufacturing\\nMedia & Entertainment\\nRetail\\nService Providers\\nSolutions Architecture Documentation\\nAnalyst Report\\nNutanix named a Leader in the Forrester Wave\\u2122: Multicloud Container Platforms, Q3 2025.\\nNutanix Cloud Infrastructure (NCI):\\nNutanix Data Services for Kubernetes (NDK)\\nProducts:\\nNutanix Kubernetes Platform, Nutanix Kubernetes Platform (NKP)\\nResource Type:\\nAnalyst Report\\nUse Cases:\\nCloud Native\\nDecember 4, 2025\\nAccess the Report\\nPartners\\nPartners\\nPartner Network\\nFind a Partner\\nTechnology Alliances\\nSystem Integrators\\nOEM Partnerships\\nConsulting Partners\\nTraining Providers\\nReseller Partners\\nService Providers\\nNot Yet a Partner?\\nBecome a Partner\\nAlready a Partner?\\nLogin\\nRequest Portal Access\\nXPAND Demand Center\\nUncertain about virtualization vendors? Partner with us.\\nDecember 30, 2024\\nGet Started Now\\nResources\\nResources\\nRead\\nBlog\\nBusiness Value\\nResources Library\\nAnalyst Reports\\nCustomer Stories\\nGlossary\\nHow to\\nThe Forecast\\nExecutive Focus\\nNewsroom\\nTech Center\\nHybrid Multicloud Hub\\nWatch\\nOn-Demand Webinars\\nVideos\\nAttend\\nEvents and Webinars\\nTraining\\nCertifications\\nBootcamp\\nConnect\\nSupport & Services\\nPartner Portal\\nCommunity\\nDeveloper Portal\\nExecutive Briefing Experience\\nNutanix User Group\\nContact Us\\nGet Started\\nCommunity Edition\\nTest Drive\\nGet a Demo\\nGet instant hands-on experience with no set-up or downloads\\nNovember 12, 2024\\nTake a Test Drive\\nTry Nutanix\\nSearch\\nNutanix Glossary\\nWhat is Cloud Native? Understanding Cloud Native Architecture\\nDecember 12, 2025 8:53 pm\\n|\\nmin\\nWhat is cloud native?\\nCloud native application architecture characteristics\\nWhat are the benefits of adopting a cloud-native approach?\\nDesigning, migrating, and deploying cloud native applications\\nHow does cloud native support DevOps practices and continuous delivery?\\nGoing cloud native? Nutanix can help\\nCloud native FAQs\\nResources\\nProducts and solutions\\nWhat is cloud native?\\nCloud native is a modern approach to building and running applications with a modular architecture that prioritizes development velocity, scalability, flexibility, and resilience. Cloud native architecture is well suited for dynamic cloud environments\\u2014whether public, private, or hybrid\\u2013which offer fungible compute and platform resources such as data services that can be used as building blocks. It leverages a combination of microservices, linux containers, and orchestration platforms like Kubernetes to create applications that are scalable, resilient, and agile. This architecture enables development teams to build, deploy, and update services independently and frequently, significantly accelerating innovation and responsiveness to evolving business needs.\\nAnalyst Report\\nNutanix named a Leader in the Forrester Wave\\u2122:\\nMulticloud Container Platforms, Q3 2025.\\nNutanix Cloud Infrastructure (NCI):\\nNutanix Data Services for Kubernetes (NDK)\\nProducts:\\nNutanix Kubernetes Platform, Nutanix Kubernetes Platform (NKP)\\nResource Type:\\nAnalyst Report\\nUse Cases:\\nCloud Native\\nDecember 4, 2025\\nLearn More\\nWhat is a cloud native application?\\nA cloud native application is engineered to operate as a distributed system, optimized for dynamic cloud infrastructure. Rather than relying on static servers or tightly coupled components, these applications are designed to be modular, stateless where possible, and infrastructure-agnostic. They integrate deeply with cloud services\\u2014such as managed databases, messaging systems, and autoscaling groups\\u2014to achieve elasticity, fault tolerance, and operational efficiency. Cloud native applications prioritize automation, observability, and rapid deployment cycles, enabling teams to deliver features and fixes continuously while maintaining system reliability and performance at scale.\\nCloud native vs cloud-enabled solutions\\nSometimes the terms \\u201ccloud native\\u201d and \\u201ccloud-enabled\\u201d are mistakenly used interchangeably when they represent two very different concepts.\\u00a0\\nCloud-enabled typically means altered or retrofitted to operate in the cloud. For instance, cloud-enabled applications are applications that might have once resided on-premises but were then rearchitected or rebuilt for a cloud platform. Rearchitecting can be a lot of work and getting an on-premises application to work in the cloud will likely come with some challenges. At the very least, a rearchitected app won\\u2019t provide the inherent agility and flexibility of cloud native applications.\\nWhile cloud-enabled applications use a variety of\\ncloud services\\n, they typically still depend on some on-premises infrastructure to run in the cloud.\\u00a0\\nSome of the major differences between cloud-enabled and cloud native applications include:\\u00a0\\nOriginal design\\n\\u2013\\u00a0While cloud native apps are developed with cloud services and technologies in mind, cloud-enabled applications must be adapted to operate in the cloud.\\u00a0\\nArchitecture\\n\\u2013\\u00a0A distributed architecture that uses microservices is common in cloud native applications; cloud-enabled applications are built using a more traditional architecture.\\nResource utilization\\n\\u2013 Optimizing the usage of resources is an inherent part of cloud native applications, allowing for dynamic scaling and a high degree of flexibility. Cloud-enabled applications aren\\u2019t designed to take advantage of cloud resource optimization features.\\u00a0\\nResilience\\n\\u2013\\u00a0Part of being cloud native is leveraging reliability capabilities such as built-in redundancy and automatic failover. Cloud-enabled applications don\\u2019t typically include those capabilities unless they\\u2019re purposely built in during the rearchitecting phase.\\u00a0\\nCloud native application examples\\nThe capabilities and benefits of cloud native applications make them ideal for situations where flexible deployment, high availability, and ultra-fast scalability are a must. Some of the components that enable that type of performance include:\\u00a0\\nMicroservices architecture\\nand continuous integration and deployment (CI\\/CD)\\n\\u2013\\u00a0By creating an application as a collection of small, independent services, developers can update separate pieces of an application without affecting the rest of it. CI\\/CD enables rapid, frequent updates and bug fixes.\\nUltra-scalability\\n\\u2013\\u00a0Cloud native applications can handle rapid fluctuations in demand and traffic because they can scale up or down quickly and easily. That\\u2019s a good capability to have in businesses such as retail, where online purchasing can hit massive demand peaks during certain times of the year.\\nThe following are some examples of use cases that benefit significantly from cloud-native applications and capabilities:\\nE-commerce platforms\\n\\u2013\\u00a0Cloud native applications provide elastic scaling to accommodate massive fluctuations in traffic and user demand.\\nStreaming media platforms\\n\\u2013\\u00a0Whether music, movies, or gaming, these online platforms can go through various periods of high traffic and demand, and need to be able to deliver 24\\/7.\\nLive chat platforms\\n\\u2013\\u00a0Live chat traffic can also fluctuate greatly depending on a number of factors, and cloud native applications can assign server resources dynamically to keep everyone connected and talking.\\nDigital banking\\n\\u2013\\u00a0Microservices enable a range of banking functions and also enable quick software updates. Containers enhance online security, which is critical in this industry.\\nMedical imaging and data analytics platform\\n\\u2013\\u00a0Cloud native technologies ensure resilience and scalability to enable fast data processing and analytics for better patient outcomes.\\nProperty rental platforms\\n\\u2013\\u00a0Large platforms such as AirBnB or VRBO use cloud native applications to deliver dynamic scaling for millions of listings. Containers and microservices keep the platform reliable and available.\\nReal-time data analytics\\n\\u2013\\u00a0Any system that provides real-time analytics requires an architecture that can keep up with enormous volumes of data from a range of sources. The distributed nature of cloud native applications is made for this.\\nCustomized consumer recommendations\\n\\u2013\\u00a0Cloud native applications use microservices to process and analyze consumer behavior and preferences so they can offer up personalized product or service recommendations.\\nAutomated \\u201csmart home\\u201d systems\\n\\u2013\\u00a0Cloud native applications use a variety of APIs to automatically manage connected appliances and allow users to interface and input commands.\\nLocation-enabled services integration\\n\\u2013\\u00a0An application such as Google Maps uses APIs to allow application developers to integrate tried-and-proven mapping capabilities into their new products.\\nLearn how to build an efficient microservices architecture.\\nCloud native application architecture characteristics\\nTraditional applications were designed to run as a single instance with all functionality required, which could be deployed to larger and more powerful servers to handle increasing demand. They were also typically created for a specific platform or operating system. Improving or updating these apps was difficult and time-consuming.\\nCloud native applications, on the other hand, are modular. They\\u2019re built with microservices which helps them to be much more flexible, scalable, and resilient than legacy apps. They all typically include the following components:\\nMicroservices\\nInstead of building all of an application\\u2019s functionality into a single service, cloud native apps are built with\\u00a0 microservices. Developers break up an application into discrete packages of code, each of which focuses on a single, specific business capability. Loosely coupled, they work collectively to create the full application and its services. Microservices are packed into containers and communicate with other microservices as needed using application programming interfaces (APIs).\\nContainers\\nThese are lightweight, isolated runtime environments that contain an individual microservice along with its system tools, libraries, and other dependencies. Because containerized microservices can operate independently of any underlying hardware or operating system\\u2014as well as other containerized microservices\\u2014they can be deployed in almost any environment and don\\u2019t interfere with other microservices.\\nAPIs\\nApplication programming interfaces (APIs) are standardized protocols that enable pieces of software to communicate with each other. APIs are what allow each containerized microservice to communicate with each other or with other services that make up the application. They can be considered the glue that connects microservices together. In a cloud native application, an API between two microservices will communicate what each microservice wants and the data it can give the other.\\nOrchestration\\nContainerized microservices and APIs are all managed dynamically via orchestration tools, such as Kubernetes.\\u00a0 These orchestration tools can manage the often-complex lifecycles of cloud native applications, as well as optimize the allocation of resources, balance loads as needed, restart a container if it experiences a failure, scale out an application as load increases, and deploy and provision containerized microservices onto servers.\\nFive Must-Haves to Successfully Navigate Your Cloud Native Journey\\nWhat are the benefits of adopting a cloud native approach?\\nIncreased scalability\\n\\u2013\\u00a0Scalability is greatly simplified with cloud native workloads because each microservice is isolated, enabling them to scale independently. The architecture allows operators to update different application components individually and makes resource allocation more efficient while avoiding under- or over-provisioning.\\nEnhanced resilience\\n\\u2013\\u00a0Isolating microservices means that if one fails, it won\\u2019t affect other relevant microservices. This can help reduce the risk of downtime and ensure that an application stays up and running. Additionally, some container solutions such as\\nKubernetes\\ncome with features that can self-heal some faults and automatically recover to maintain high resilience.\\nGreater efficiency\\n-\\u00a0Cloud native application development enables organizations to adopt a DevOps approach, which includes continuous integration and continuous delivery (CD). Cloud native development also leverages a range of\\ncloud services\\nand\\u00a0automated tools to accelerate and streamline the way developers build applications.\\nPortability across different infrastructures\\n\\u2013\\u00a0Containers allow organizations to avoid vendor lock-in and make it easy to move applications where they\\u2019re needed, regardless of cloud platform or provider. This portability is especially beneficial for the increasingly popular\\nhybrid multicloud infrastructure\\n.\\u00a0Some organizations even distribute an application across multiple providers for increased flexibility and stability.\\nEasier deployment and management\\n\\u2013\\u00a0Cloud native applications make good use of automation to deploy specific application features or update apps. Developers can also use automation to enable CI\\/CD and improve applications without disrupting the ongoing user experience.\\nReduced costs\\n\\u2013\\u00a0Because development, testing, and application hosting take place in the cloud, there\\u2019s no need to purchase (or manage and maintain) additional hardware, which can come with the risk and cost of overprovisioning. Cloud deployments are typically pay-as-you-use so organizations can get the resources they need in the moment. Simpler development, deployment, and management of applications can also help organizations save on developer and IT costs and effort, while providing those employees more time to focus on more critical projects.\\nIncreased availability\\n\\u2013\\u00a0IT can update cloud native applications without causing any downtime, to keep services available whenever they\\u2019re needed. Also, it\\u2019s simple to spin up new application resources at a moment\\u2019s notice in the cloud, so operations stay consistently available even when demand spikes rapidly, such as during peak online shopping seasons.\\nImproved agility and productivity\\n\\u2013\\u00a0Cloud native applications allow for a range of deployment options, so organizations can deploy them how and where they want. The modular nature of cloud native apps also enables fast and flexible development, testing, and deployment of new features. When DevOps teams use a cloud native approach to applications, they simplify the development process; troubleshoot and iterate faster and more efficiently; and speed up time to market, which helps organizations respond more effectively to shifting trends and customer demands.\\nDesigning, migrating, and deploying cloud native applications\\nCloud native application development is the modern approach to building scalable, flexible, resilient applications. For organizations\\nmigrating\\nfrom on-premises environments or designing new workloads in the cloud, the following practices can simplify the process and reduce risk.\\nPlanning and preparation\\nApplication migration can be a challenge, especially when moving an app from an on-premises environment to the cloud. However, you can make it easier and more seamless with some planning and preparation.\\nThe planning phase includes the following actions:\\nPortfolio evaluation\\n\\u2013 Assess your organization\\u2019s current applications to determine which ones are best suited to cloud migration. Relevant criteria should include the business value of moving the application, how complex it will be, and whether it\\u2019s technically feasible.\\nAssessment of changes needed\\n\\u2013 Note which applications will need to be redesigned, refactored, or reauthored, and in what ways. This will typically entail identifying how to break apps down into microservices, implement containers, and so on.\\nCloud provider engagement\\n\\u2013 Decide which cloud provider you\\u2019ll use to migrate your applications. Important factors in this selection include level of support, pricing, services provided, and compliance.\\nArchitecture and tooling\\nOnce planning has been completed, it\\u2019s time to actually migrate or build applications with the right tools:\\nBreaking into microservices and\\ncontainerizing\\nthem\\n\\u2013 Applications are decomposed into microservices and packaged into containers with all dependencies included, ensuring portability and consistency across environments.\\nImplementing\\u00a0 orchestration with Kubernetes\\n\\u2013 A container orchestration platform such as Kubernetes manages deployment, scaling, and lifecycle operations. It automates resource allocation and ensures applications remain resilient.\\nPreparing the destination server architecture\\n\\u2013 The cloud environment must be configured for speed, bandwidth, redundancy, and security requirements to handle workloads effectively.\\nMicroservices and lightweight containers\\n\\u2013 Microservices and containers simplify development and operations, making it easier to manage, update, and improve applications over time.\\nChoose tools that enhance efficiency\\n\\u2013 The technology stack should align with the application\\u2019s requirements. Some solutions are best suited for data processing, while others may work better for microservice creation and management.\\nDeployment and best practices\\nWhether migrating existing applications or deploying new ones, best practices ensure long-term resilience:\\nCI\\/CD for better productivity\\n\\u2013 Continuous integration ensures developers always work with the latest code, while continuous delivery automates deployment to production. This improves communication, reduces bugs, and accelerates time to market.\\nImmutable infrastructure with IaC\\n\\u2013 Infrastructure as code automates and standardizes resource management, ensuring predictable and stable deployments. IaC boosts safety and efficiency by creating new instances instead of modifying existing ones.\\nServerless to eliminate management overhead\\n\\u2013 Going serverless removes the need to manage servers directly. Developers only pay for resources consumed, scaling is fast, and compliance\\/security features are often built in.\\nSecurity as a priority\\n\\u2013 Integrate access control, encryption, network security, and intrusion detection throughout development. A \\u201cshift-left\\u201d security approach ensures resilience from the start.\\nObservability to detect issues quickly\\n\\u2013 Gather logs, metrics, and traces across applications and infrastructure to diagnose failures or vulnerabilities in real time.\\nService meshes for optimized communication\\n\\u2013 Service meshes simplify inter-service communication, letting developers focus on building features rather than managing complex networking details.\\nValidation and monitoring\\nTesting in cloud native environments\\n\\u2013 Deploy and comprehensively test critical components before production migration.\\nData migration\\n\\u2013 Move application data into\\ncloud storage\\nwhile maintaining integrity and consistency, and reconfigure applications to run correctly in the new environment.\\nOngoing monitoring\\n\\u2013 Once deployed, monitor performance, scalability, and resource allocation continuously. Stay aware that problems can arise in any stage, and it can take several weeks to feel confident that an application is stable in its new cloud-based environment.\\neBook\\nA Cloud Native Playbook for Platform Engineers\\nProducts:\\nNutanix Kubernetes Platform (NKP)\\nResource Type:\\neBook\\nUse Cases:\\nCloud Native\\nOctober 19, 2025\\nLearn More\\nHow does cloud native support DevOps practices and continuous delivery?\\nCloud computing\\n\\u00a0enabled the era of DevOps, which is essentially a partnership between IT operations (Ops) and software development (Dev) teams. It focuses on integration of processes as well as collaboration and effective communication. The ability to scale in the cloud and easily, seamlessly provision resources on demand made DevOps possible, an approach that values fast, efficient application development, testing, and deployment with many small iterations along the way.\\nWhen organizations take on a cloud native approach to applications and computing, they also enable the benefits of continuous integration (CI) and continuous delivery (CD), which help lead to applications that are extremely resilient, observable, scalable, and manageable.\\nWhile cloud computing paved the way for DevOps, DevOps also in turn helped the cloud evolve, through a high degree\\u00a0of\\nautomation\\nand\\u00a0\\u00a0increased collaboration between software development and IT operations. DevOps practices are able to flourish in the cloud and cloud native application development is fast becoming imperative for any organization that wants to stay competitive in today\\u2019s fierce marketplace.\\nGoing cloud native? Nutanix can help\\nNutanix understands the modern infrastructure challenges that today\\u2019s organizations face\\u2014and has developed solutions to ease those difficulties and help your business thrive. We offer\\nhyperconverged infrastructure\\n(HCI) and\\nhybrid multicloud solutions\\nthat can make it simple to both build and deploy new apps in the cloud and migrate existing applications to the cloud.\\nWith\\nNutanix Kubernetes Platform (NKP)\\n\\u2122\\n, you can speed time to market and innovate more quickly with easy container management across hybrid, multicloud, and on-premises environments. Add in\\nNutanix Data Services for Kubernetes (NDK)\\n\\u2122\\nand you get a range of advanced data services designed specifically for cloud-native environments. Using the two solutions together, you can:\\nDevelop applications faster\\nSimplify development, testing, and deployment with automation\\nGet instant platform engineering with APIs and GitOps workflows\\nGain deep insight into all clusters and environments from a single pane of glass\\nEnjoy enterprise-class security features built in and designed to meet strict security standards\\nControl cloud-native apps at the application layer\\nSimplify and unify provisioning and operation of cloud-native apps\\nAnd much more\\nCloud Native FAQs\\nWhat is cloud native in simple terms?\\nCloud native is an approach to building and running applications using modular architectures that prioritize speed, scalability, and resilience. It leverages microservices, Linux containers, and orchestration tools like Kubernetes to enable frequent, independent updates and rapid innovation across dynamic cloud environments.\\nWhat is the difference between cloud native and cloud enabled?\\nCloud native applications are architected specifically for cloud environments, using containers, microservices, APIs, and orchestration tools like Kubernetes. Cloud-enabled apps are traditional applications rehosted or refactored for the cloud, often retaining monolithic dependencies and limited flexibility compared to true cloud native solutions.\\nWhy is cloud native important for enterprise IT?\\nCloud native accelerates digital transformation by enabling continuous delivery, rapid scaling, and operational resilience. For enterprises, this means faster innovation cycles, reduced downtime, and the flexibility to run workloads across private, public, or hybrid multicloud environments without vendor lock-in.\\nHow does cloud native support DevOps practices?\\nCloud native architecture aligns with DevOps by supporting continuous integration and delivery (CI\\/CD), automated testing pipelines, and infrastructure as code. These capabilities allow IT teams to push frequent, reliable updates and manage application lifecycles seamlessly across hybrid and multicloud environments.\\nWhat role does Kubernetes play in cloud native architecture?\\nKubernetes is the orchestration layer for cloud native applications, automating container deployment, scaling, load balancing, and self-healing. It ensures microservices run efficiently across clusters, making it essential for managing complex, distributed applications at enterprise scale.\\nExplore our top resources\\nFast-Track Your Cloud-Native Journey\\nNovember 12, 2024\\nTest Drive NKP\\nAnalyst Report\\nNutanix named a Challenger in the 2025 Gartner\\u00ae Magic Quadrant\\u2122 for Container Management.\\u00a0\\nNutanix Cloud Infrastructure (NCI):\\nNutanix Data Services for Kubernetes (NDK)\\nProducts:\\nNutanix Kubernetes Platform, Nutanix Kubernetes Platform (NKP)\\nResource Type:\\nAnalyst Report\\nUse Cases:\\nCloud Native\\nNovember 13, 2025\\nRead the analyst report\\n7 Crucial Steps to Kubernetes Adoption\\nRead the infographic\\nTech Note:\\u00a0Red Hat OpenShift on Nutanix\\nLearn More\\nNutanix Validated Design:\\u00a0AOS 6.5 with Red Hat OpenShift Design\\nLearn More\\nRelated products and solutions\\nNutanix Data Services for Kubernetes (NDK)\\nNDK simplifies and unifies provisioning and operating cloud-native applications by extending enterprise data services to containerized apps.\\nNutanix Cloud Infrastructure (NCI):\\nNutanix Data Services for Kubernetes (NDK)\\nUse Cases:\\nCloud Native\\nFebruary 4, 2025\\nLearn more about NDK\\nNutanix Kubernetes Platform\\nNutanix Kubernetes Platform (NKP) simplifies platform engineering by reducing operational complexity and establishing consistency across any environment.\\nProducts:\\nNutanix Kubernetes Platform (NKP)\\nUse Cases:\\nCloud Native\\nFebruary 4, 2025\\nLearn more about NKP\\nSimplify Kubernetes Across Hybrid and Multicloud Environments\\nNKP speeds your Kubernetes journey with a single, centralized control point to run apps across distributed, diverse infrastructures.\\nProducts:\\nNutanix Kubernetes Platform (NKP)\\nUse Cases:\\nCloud Native\\nJuly 11, 2025\\nLearn more\\nLearn more about cloud native\\nCloud automation\\nCloud automation is the use of diverse tools and services by businesses to eliminate the laborious and time-consuming tasks associated with manually operating components of the cloud.\\nJanuary 29, 2024\\nLearn more\\nContainerization\\nDiscover the power of containerization with Nutanix. Learn how it streamlines deployment, enhances scalability, and boosts application efficiency.\\nAugust 8, 2024\\nLearn more\\nEdge computing\\nxplore edge computing with Nutanix. Learn what it is, how it works, benefits, challenges, and use cases.\\nUse Cases:\\nEdge and Remote Sites (ROBO)\\nJuly 15, 2025\\nLearn more\\nHybrid cloud\\nHybrid cloud computing combines on-premise IT with off-premise resources or services. Learn more about how hybrid cloud works and the benefits it can bring.\\nKey Play:\\nHybrid Cloud\\nUse Cases:\\nHybrid Multicloud\\nJuly 7, 2025\\nLearn more\\nKubernetes\\nLearn everything to know about Kubernetes, an open-source software for automating processes in deploying, scaling, and managing containerized applications.\\nJune 20, 2023\\nLearn more\\nMulticloud\\u00a0\\nMulticloud is the use of more than one cloud platform that delivers a specific application or service and can be comprised of public, private, and edge clouds.\\nKey Play:\\nHybrid Cloud\\nUse Cases:\\nHybrid Multicloud\\nSeptember 3, 2024\\nLearn more\\nWhat We Do\\nSolutions\\nProducts\\nResources\\nOur Customers\\nTech Terms\\nCompany\\nCareers\\nGlobal Offices\\nLeadership\\nNewsroom\\nInvestor Relations\\nSocial Responsibility\\nTrust\\nSupport\\nSupport Portal Login\\nContact Support\\nProduct Support\\nContact Us\\nPartner Login\\nBlog\\nThe Forecast\\nDeveloper Portal\\nExecutive Focus\\nEvents\\nWebinars on Demand\\n\\u00a9 Nutanix 2026\\nTerms of Use\\nPrivacy Statement\\nDo Not Sell or Share My Personal Information\\nTerms of Use\\nPrivacy Statement\\nDo Not Sell or Share My Personal Information\\n\"}"
},
"response": {
"status": "false",
"response": "false"
}
} {
"prompt": {
"label": "resume_data",
"prompt": {
"prompt_id": "7",
"prompt_label": "resume_data",
"content_format": "{\"data\":\"content\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you."
},
"content": "{\"data\":\"Support\\nServices\\nContact Us\\nEnglish\\nDeutschland (Deutsch)\\nEspa\\u00f1a (Espa\\u00f1ol)\\nFrance (Fran\\u00e7ais)\\nItalia (Italiano)\\nEnglish\\n\\u65e5\\u672c (\\u65e5\\u672c\\u8a9e)\\n\\ub300\\ud55c\\ubbfc\\uad6d(KR)\\nLatinoam\\u00e9rica (Espa\\u00f1ol)\\nBrasil (Portugu\\u00eas)\\n\\u53f0\\u7063 (\\u7e41\\u9ad4\\u4e2d\\u6587)\\nUnited Kingdom (English)\\nAustralia (English)\\nAsia Pacific (English)\\nGo to Section\\nWhat We Do\\nProducts\\nProducts\\nNutanix Cloud Platform\\nNutanix Central\\nNutanix Central\\nPrism\\nNutanix Cloud Infrastructure\\nNutanix Cloud Infrastructure\\nAOS Storage\\nAHV Virtualization\\nNutanix Disaster Recovery\\nFlow Network Security\\nFlow Virtual Networking\\nNutanix Cloud Clusters (NC2)\\nNutanix Government Cloud Clusters (GC2)\\nNCI with External Storage\\nNutanix Database Service\\nNutanix Kubernetes\\u00ae Platform\\nNutanix Kubernetes\\u00ae Platform\\nNutanix Data Services for Kubernetes\\nCloud Native AOS\\nMulticloud Kubernetes\\nNutanix Cloud Manager\\nNutanix Cloud Manager\\nIntelligent Operations\\nSelf-Service\\nCost Governance\\nSecurity Central\\nNutanix Unified Storage\\nNutanix Unified Storage\\nFiles Storage\\nObjects Storage\\nVolumes Block Storage\\nNutanix Data Lens\\nNutanix Enterprise AI\\nFor Deployment Success\\nNutanix Move\\nHardware Platforms\\nSoftware Options\\nCommunity Edition\\nSizer Configuration Estimator\\nX-Ray Performance & Reliability Tests\\nLCM Full-stack Update Manager\\nInsights Support Automation\\nA Leader in the 2025 Gartner\\u00ae Magic Quadrant\\u2122 for Distributed Hybrid Infrastructure\\nSee Why\\nSolutions\\nSolutions\\nKey Solutions\\nVMware Alternative\\nHybrid Cloud Adoption\\nKubernetes Platform\\nCloud\\nBusiness Continuity & Disaster Recovery\\nBusiness-Critical Apps\\nCloud Native\\nDigital Sovereignty\\nEdge (& ROBO)\\nHybrid Multicloud\\nMigrate Applications to Cloud\\nPrivate Cloud\\nSecurity\\nSustainability & IT\\nDatabases\\nDatabase-as-a-Service\\nEnd-User Computing (VDI and DaaS)\\nCitrix\\nEnd-User Computing\\nApplications\\nAI \\/ ML\\nIndustry Solutions\\nAutomotive\\nFinancial Services\\nGovernment and Education\\nHealthcare\\nLegal\\nManufacturing\\nMedia & Entertainment\\nRetail\\nService Providers\\nSolutions Architecture Documentation\\nAnalyst Report\\nNutanix named a Leader in the Forrester Wave\\u2122: Multicloud Container Platforms, Q3 2025.\\nNutanix Cloud Infrastructure (NCI):\\nNutanix Data Services for Kubernetes (NDK)\\nProducts:\\nNutanix Kubernetes Platform, Nutanix Kubernetes Platform (NKP)\\nResource Type:\\nAnalyst Report\\nUse Cases:\\nCloud Native\\nDecember 4, 2025\\nAccess the Report\\nPartners\\nPartners\\nPartner Network\\nFind a Partner\\nTechnology Alliances\\nSystem Integrators\\nOEM Partnerships\\nConsulting Partners\\nTraining Providers\\nReseller Partners\\nService Providers\\nNot Yet a Partner?\\nBecome a Partner\\nAlready a Partner?\\nLogin\\nRequest Portal Access\\nXPAND Demand Center\\nUncertain about virtualization vendors? Partner with us.\\nDecember 30, 2024\\nGet Started Now\\nResources\\nResources\\nRead\\nBlog\\nBusiness Value\\nResources Library\\nAnalyst Reports\\nCustomer Stories\\nGlossary\\nHow to\\nThe Forecast\\nExecutive Focus\\nNewsroom\\nTech Center\\nHybrid Multicloud Hub\\nWatch\\nOn-Demand Webinars\\nVideos\\nAttend\\nEvents and Webinars\\nTraining\\nCertifications\\nBootcamp\\nConnect\\nSupport & Services\\nPartner Portal\\nCommunity\\nDeveloper Portal\\nExecutive Briefing Experience\\nNutanix User Group\\nContact Us\\nGet Started\\nCommunity Edition\\nTest Drive\\nGet a Demo\\nGet instant hands-on experience with no set-up or downloads\\nNovember 12, 2024\\nTake a Test Drive\\nTry Nutanix\\nSearch\\nNutanix Glossary\\nWhat is Cloud Native? Understanding Cloud Native Architecture\\nDecember 12, 2025 8:53 pm\\n|\\nmin\\nWhat is cloud native?\\nCloud native application architecture characteristics\\nWhat are the benefits of adopting a cloud-native approach?\\nDesigning, migrating, and deploying cloud native applications\\nHow does cloud native support DevOps practices and continuous delivery?\\nGoing cloud native? Nutanix can help\\nCloud native FAQs\\nResources\\nProducts and solutions\\nWhat is cloud native?\\nCloud native is a modern approach to building and running applications with a modular architecture that prioritizes development velocity, scalability, flexibility, and resilience. Cloud native architecture is well suited for dynamic cloud environments\\u2014whether public, private, or hybrid\\u2013which offer fungible compute and platform resources such as data services that can be used as building blocks. It leverages a combination of microservices, linux containers, and orchestration platforms like Kubernetes to create applications that are scalable, resilient, and agile. This architecture enables development teams to build, deploy, and update services independently and frequently, significantly accelerating innovation and responsiveness to evolving business needs.\\nAnalyst Report\\nNutanix named a Leader in the Forrester Wave\\u2122:\\nMulticloud Container Platforms, Q3 2025.\\nNutanix Cloud Infrastructure (NCI):\\nNutanix Data Services for Kubernetes (NDK)\\nProducts:\\nNutanix Kubernetes Platform, Nutanix Kubernetes Platform (NKP)\\nResource Type:\\nAnalyst Report\\nUse Cases:\\nCloud Native\\nDecember 4, 2025\\nLearn More\\nWhat is a cloud native application?\\nA cloud native application is engineered to operate as a distributed system, optimized for dynamic cloud infrastructure. Rather than relying on static servers or tightly coupled components, these applications are designed to be modular, stateless where possible, and infrastructure-agnostic. They integrate deeply with cloud services\\u2014such as managed databases, messaging systems, and autoscaling groups\\u2014to achieve elasticity, fault tolerance, and operational efficiency. Cloud native applications prioritize automation, observability, and rapid deployment cycles, enabling teams to deliver features and fixes continuously while maintaining system reliability and performance at scale.\\nCloud native vs cloud-enabled solutions\\nSometimes the terms \\u201ccloud native\\u201d and \\u201ccloud-enabled\\u201d are mistakenly used interchangeably when they represent two very different concepts.\\u00a0\\nCloud-enabled typically means altered or retrofitted to operate in the cloud. For instance, cloud-enabled applications are applications that might have once resided on-premises but were then rearchitected or rebuilt for a cloud platform. Rearchitecting can be a lot of work and getting an on-premises application to work in the cloud will likely come with some challenges. At the very least, a rearchitected app won\\u2019t provide the inherent agility and flexibility of cloud native applications.\\nWhile cloud-enabled applications use a variety of\\ncloud services\\n, they typically still depend on some on-premises infrastructure to run in the cloud.\\u00a0\\nSome of the major differences between cloud-enabled and cloud native applications include:\\u00a0\\nOriginal design\\n\\u2013\\u00a0While cloud native apps are developed with cloud services and technologies in mind, cloud-enabled applications must be adapted to operate in the cloud.\\u00a0\\nArchitecture\\n\\u2013\\u00a0A distributed architecture that uses microservices is common in cloud native applications; cloud-enabled applications are built using a more traditional architecture.\\nResource utilization\\n\\u2013 Optimizing the usage of resources is an inherent part of cloud native applications, allowing for dynamic scaling and a high degree of flexibility. Cloud-enabled applications aren\\u2019t designed to take advantage of cloud resource optimization features.\\u00a0\\nResilience\\n\\u2013\\u00a0Part of being cloud native is leveraging reliability capabilities such as built-in redundancy and automatic failover. Cloud-enabled applications don\\u2019t typically include those capabilities unless they\\u2019re purposely built in during the rearchitecting phase.\\u00a0\\nCloud native application examples\\nThe capabilities and benefits of cloud native applications make them ideal for situations where flexible deployment, high availability, and ultra-fast scalability are a must. Some of the components that enable that type of performance include:\\u00a0\\nMicroservices architecture\\nand continuous integration and deployment (CI\\/CD)\\n\\u2013\\u00a0By creating an application as a collection of small, independent services, developers can update separate pieces of an application without affecting the rest of it. CI\\/CD enables rapid, frequent updates and bug fixes.\\nUltra-scalability\\n\\u2013\\u00a0Cloud native applications can handle rapid fluctuations in demand and traffic because they can scale up or down quickly and easily. That\\u2019s a good capability to have in businesses such as retail, where online purchasing can hit massive demand peaks during certain times of the year.\\nThe following are some examples of use cases that benefit significantly from cloud-native applications and capabilities:\\nE-commerce platforms\\n\\u2013\\u00a0Cloud native applications provide elastic scaling to accommodate massive fluctuations in traffic and user demand.\\nStreaming media platforms\\n\\u2013\\u00a0Whether music, movies, or gaming, these online platforms can go through various periods of high traffic and demand, and need to be able to deliver 24\\/7.\\nLive chat platforms\\n\\u2013\\u00a0Live chat traffic can also fluctuate greatly depending on a number of factors, and cloud native applications can assign server resources dynamically to keep everyone connected and talking.\\nDigital banking\\n\\u2013\\u00a0Microservices enable a range of banking functions and also enable quick software updates. Containers enhance online security, which is critical in this industry.\\nMedical imaging and data analytics platform\\n\\u2013\\u00a0Cloud native technologies ensure resilience and scalability to enable fast data processing and analytics for better patient outcomes.\\nProperty rental platforms\\n\\u2013\\u00a0Large platforms such as AirBnB or VRBO use cloud native applications to deliver dynamic scaling for millions of listings. Containers and microservices keep the platform reliable and available.\\nReal-time data analytics\\n\\u2013\\u00a0Any system that provides real-time analytics requires an architecture that can keep up with enormous volumes of data from a range of sources. The distributed nature of cloud native applications is made for this.\\nCustomized consumer recommendations\\n\\u2013\\u00a0Cloud native applications use microservices to process and analyze consumer behavior and preferences so they can offer up personalized product or service recommendations.\\nAutomated \\u201csmart home\\u201d systems\\n\\u2013\\u00a0Cloud native applications use a variety of APIs to automatically manage connected appliances and allow users to interface and input commands.\\nLocation-enabled services integration\\n\\u2013\\u00a0An application such as Google Maps uses APIs to allow application developers to integrate tried-and-proven mapping capabilities into their new products.\\nLearn how to build an efficient microservices architecture.\\nCloud native application architecture characteristics\\nTraditional applications were designed to run as a single instance with all functionality required, which could be deployed to larger and more powerful servers to handle increasing demand. They were also typically created for a specific platform or operating system. Improving or updating these apps was difficult and time-consuming.\\nCloud native applications, on the other hand, are modular. They\\u2019re built with microservices which helps them to be much more flexible, scalable, and resilient than legacy apps. They all typically include the following components:\\nMicroservices\\nInstead of building all of an application\\u2019s functionality into a single service, cloud native apps are built with\\u00a0 microservices. Developers break up an application into discrete packages of code, each of which focuses on a single, specific business capability. Loosely coupled, they work collectively to create the full application and its services. Microservices are packed into containers and communicate with other microservices as needed using application programming interfaces (APIs).\\nContainers\\nThese are lightweight, isolated runtime environments that contain an individual microservice along with its system tools, libraries, and other dependencies. Because containerized microservices can operate independently of any underlying hardware or operating system\\u2014as well as other containerized microservices\\u2014they can be deployed in almost any environment and don\\u2019t interfere with other microservices.\\nAPIs\\nApplication programming interfaces (APIs) are standardized protocols that enable pieces of software to communicate with each other. APIs are what allow each containerized microservice to communicate with each other or with other services that make up the application. They can be considered the glue that connects microservices together. In a cloud native application, an API between two microservices will communicate what each microservice wants and the data it can give the other.\\nOrchestration\\nContainerized microservices and APIs are all managed dynamically via orchestration tools, such as Kubernetes.\\u00a0 These orchestration tools can manage the often-complex lifecycles of cloud native applications, as well as optimize the allocation of resources, balance loads as needed, restart a container if it experiences a failure, scale out an application as load increases, and deploy and provision containerized microservices onto servers.\\nFive Must-Haves to Successfully Navigate Your Cloud Native Journey\\nWhat are the benefits of adopting a cloud native approach?\\nIncreased scalability\\n\\u2013\\u00a0Scalability is greatly simplified with cloud native workloads because each microservice is isolated, enabling them to scale independently. The architecture allows operators to update different application components individually and makes resource allocation more efficient while avoiding under- or over-provisioning.\\nEnhanced resilience\\n\\u2013\\u00a0Isolating microservices means that if one fails, it won\\u2019t affect other relevant microservices. This can help reduce the risk of downtime and ensure that an application stays up and running. Additionally, some container solutions such as\\nKubernetes\\ncome with features that can self-heal some faults and automatically recover to maintain high resilience.\\nGreater efficiency\\n-\\u00a0Cloud native application development enables organizations to adopt a DevOps approach, which includes continuous integration and continuous delivery (CD). Cloud native development also leverages a range of\\ncloud services\\nand\\u00a0automated tools to accelerate and streamline the way developers build applications.\\nPortability across different infrastructures\\n\\u2013\\u00a0Containers allow organizations to avoid vendor lock-in and make it easy to move applications where they\\u2019re needed, regardless of cloud platform or provider. This portability is especially beneficial for the increasingly popular\\nhybrid multicloud infrastructure\\n.\\u00a0Some organizations even distribute an application across multiple providers for increased flexibility and stability.\\nEasier deployment and management\\n\\u2013\\u00a0Cloud native applications make good use of automation to deploy specific application features or update apps. Developers can also use automation to enable CI\\/CD and improve applications without disrupting the ongoing user experience.\\nReduced costs\\n\\u2013\\u00a0Because development, testing, and application hosting take place in the cloud, there\\u2019s no need to purchase (or manage and maintain) additional hardware, which can come with the risk and cost of overprovisioning. Cloud deployments are typically pay-as-you-use so organizations can get the resources they need in the moment. Simpler development, deployment, and management of applications can also help organizations save on developer and IT costs and effort, while providing those employees more time to focus on more critical projects.\\nIncreased availability\\n\\u2013\\u00a0IT can update cloud native applications without causing any downtime, to keep services available whenever they\\u2019re needed. Also, it\\u2019s simple to spin up new application resources at a moment\\u2019s notice in the cloud, so operations stay consistently available even when demand spikes rapidly, such as during peak online shopping seasons.\\nImproved agility and productivity\\n\\u2013\\u00a0Cloud native applications allow for a range of deployment options, so organizations can deploy them how and where they want. The modular nature of cloud native apps also enables fast and flexible development, testing, and deployment of new features. When DevOps teams use a cloud native approach to applications, they simplify the development process; troubleshoot and iterate faster and more efficiently; and speed up time to market, which helps organizations respond more effectively to shifting trends and customer demands.\\nDesigning, migrating, and deploying cloud native applications\\nCloud native application development is the modern approach to building scalable, flexible, resilient applications. For organizations\\nmigrating\\nfrom on-premises environments or designing new workloads in the cloud, the following practices can simplify the process and reduce risk.\\nPlanning and preparation\\nApplication migration can be a challenge, especially when moving an app from an on-premises environment to the cloud. However, you can make it easier and more seamless with some planning and preparation.\\nThe planning phase includes the following actions:\\nPortfolio evaluation\\n\\u2013 Assess your organization\\u2019s current applications to determine which ones are best suited to cloud migration. Relevant criteria should include the business value of moving the application, how complex it will be, and whether it\\u2019s technically feasible.\\nAssessment of changes needed\\n\\u2013 Note which applications will need to be redesigned, refactored, or reauthored, and in what ways. This will typically entail identifying how to break apps down into microservices, implement containers, and so on.\\nCloud provider engagement\\n\\u2013 Decide which cloud provider you\\u2019ll use to migrate your applications. Important factors in this selection include level of support, pricing, services provided, and compliance.\\nArchitecture and tooling\\nOnce planning has been completed, it\\u2019s time to actually migrate or build applications with the right tools:\\nBreaking into microservices and\\ncontainerizing\\nthem\\n\\u2013 Applications are decomposed into microservices and packaged into containers with all dependencies included, ensuring portability and consistency across environments.\\nImplementing\\u00a0 orchestration with Kubernetes\\n\\u2013 A container orchestration platform such as Kubernetes manages deployment, scaling, and lifecycle operations. It automates resource allocation and ensures applications remain resilient.\\nPreparing the destination server architecture\\n\\u2013 The cloud environment must be configured for speed, bandwidth, redundancy, and security requirements to handle workloads effectively.\\nMicroservices and lightweight containers\\n\\u2013 Microservices and containers simplify development and operations, making it easier to manage, update, and improve applications over time.\\nChoose tools that enhance efficiency\\n\\u2013 The technology stack should align with the application\\u2019s requirements. Some solutions are best suited for data processing, while others may work better for microservice creation and management.\\nDeployment and best practices\\nWhether migrating existing applications or deploying new ones, best practices ensure long-term resilience:\\nCI\\/CD for better productivity\\n\\u2013 Continuous integration ensures developers always work with the latest code, while continuous delivery automates deployment to production. This improves communication, reduces bugs, and accelerates time to market.\\nImmutable infrastructure with IaC\\n\\u2013 Infrastructure as code automates and standardizes resource management, ensuring predictable and stable deployments. IaC boosts safety and efficiency by creating new instances instead of modifying existing ones.\\nServerless to eliminate management overhead\\n\\u2013 Going serverless removes the need to manage servers directly. Developers only pay for resources consumed, scaling is fast, and compliance\\/security features are often built in.\\nSecurity as a priority\\n\\u2013 Integrate access control, encryption, network security, and intrusion detection throughout development. A \\u201cshift-left\\u201d security approach ensures resilience from the start.\\nObservability to detect issues quickly\\n\\u2013 Gather logs, metrics, and traces across applications and infrastructure to diagnose failures or vulnerabilities in real time.\\nService meshes for optimized communication\\n\\u2013 Service meshes simplify inter-service communication, letting developers focus on building features rather than managing complex networking details.\\nValidation and monitoring\\nTesting in cloud native environments\\n\\u2013 Deploy and comprehensively test critical components before production migration.\\nData migration\\n\\u2013 Move application data into\\ncloud storage\\nwhile maintaining integrity and consistency, and reconfigure applications to run correctly in the new environment.\\nOngoing monitoring\\n\\u2013 Once deployed, monitor performance, scalability, and resource allocation continuously. Stay aware that problems can arise in any stage, and it can take several weeks to feel confident that an application is stable in its new cloud-based environment.\\neBook\\nA Cloud Native Playbook for Platform Engineers\\nProducts:\\nNutanix Kubernetes Platform (NKP)\\nResource Type:\\neBook\\nUse Cases:\\nCloud Native\\nOctober 19, 2025\\nLearn More\\nHow does cloud native support DevOps practices and continuous delivery?\\nCloud computing\\n\\u00a0enabled the era of DevOps, which is essentially a partnership between IT operations (Ops) and software development (Dev) teams. It focuses on integration of processes as well as collaboration and effective communication. The ability to scale in the cloud and easily, seamlessly provision resources on demand made DevOps possible, an approach that values fast, efficient application development, testing, and deployment with many small iterations along the way.\\nWhen organizations take on a cloud native approach to applications and computing, they also enable the benefits of continuous integration (CI) and continuous delivery (CD), which help lead to applications that are extremely resilient, observable, scalable, and manageable.\\nWhile cloud computing paved the way for DevOps, DevOps also in turn helped the cloud evolve, through a high degree\\u00a0of\\nautomation\\nand\\u00a0\\u00a0increased collaboration between software development and IT operations. DevOps practices are able to flourish in the cloud and cloud native application development is fast becoming imperative for any organization that wants to stay competitive in today\\u2019s fierce marketplace.\\nGoing cloud native? Nutanix can help\\nNutanix understands the modern infrastructure challenges that today\\u2019s organizations face\\u2014and has developed solutions to ease those difficulties and help your business thrive. We offer\\nhyperconverged infrastructure\\n(HCI) and\\nhybrid multicloud solutions\\nthat can make it simple to both build and deploy new apps in the cloud and migrate existing applications to the cloud.\\nWith\\nNutanix Kubernetes Platform (NKP)\\n\\u2122\\n, you can speed time to market and innovate more quickly with easy container management across hybrid, multicloud, and on-premises environments. Add in\\nNutanix Data Services for Kubernetes (NDK)\\n\\u2122\\nand you get a range of advanced data services designed specifically for cloud-native environments. Using the two solutions together, you can:\\nDevelop applications faster\\nSimplify development, testing, and deployment with automation\\nGet instant platform engineering with APIs and GitOps workflows\\nGain deep insight into all clusters and environments from a single pane of glass\\nEnjoy enterprise-class security features built in and designed to meet strict security standards\\nControl cloud-native apps at the application layer\\nSimplify and unify provisioning and operation of cloud-native apps\\nAnd much more\\nCloud Native FAQs\\nWhat is cloud native in simple terms?\\nCloud native is an approach to building and running applications using modular architectures that prioritize speed, scalability, and resilience. It leverages microservices, Linux containers, and orchestration tools like Kubernetes to enable frequent, independent updates and rapid innovation across dynamic cloud environments.\\nWhat is the difference between cloud native and cloud enabled?\\nCloud native applications are architected specifically for cloud environments, using containers, microservices, APIs, and orchestration tools like Kubernetes. Cloud-enabled apps are traditional applications rehosted or refactored for the cloud, often retaining monolithic dependencies and limited flexibility compared to true cloud native solutions.\\nWhy is cloud native important for enterprise IT?\\nCloud native accelerates digital transformation by enabling continuous delivery, rapid scaling, and operational resilience. For enterprises, this means faster innovation cycles, reduced downtime, and the flexibility to run workloads across private, public, or hybrid multicloud environments without vendor lock-in.\\nHow does cloud native support DevOps practices?\\nCloud native architecture aligns with DevOps by supporting continuous integration and delivery (CI\\/CD), automated testing pipelines, and infrastructure as code. These capabilities allow IT teams to push frequent, reliable updates and manage application lifecycles seamlessly across hybrid and multicloud environments.\\nWhat role does Kubernetes play in cloud native architecture?\\nKubernetes is the orchestration layer for cloud native applications, automating container deployment, scaling, load balancing, and self-healing. It ensures microservices run efficiently across clusters, making it essential for managing complex, distributed applications at enterprise scale.\\nExplore our top resources\\nFast-Track Your Cloud-Native Journey\\nNovember 12, 2024\\nTest Drive NKP\\nAnalyst Report\\nNutanix named a Challenger in the 2025 Gartner\\u00ae Magic Quadrant\\u2122 for Container Management.\\u00a0\\nNutanix Cloud Infrastructure (NCI):\\nNutanix Data Services for Kubernetes (NDK)\\nProducts:\\nNutanix Kubernetes Platform, Nutanix Kubernetes Platform (NKP)\\nResource Type:\\nAnalyst Report\\nUse Cases:\\nCloud Native\\nNovember 13, 2025\\nRead the analyst report\\n7 Crucial Steps to Kubernetes Adoption\\nRead the infographic\\nTech Note:\\u00a0Red Hat OpenShift on Nutanix\\nLearn More\\nNutanix Validated Design:\\u00a0AOS 6.5 with Red Hat OpenShift Design\\nLearn More\\nRelated products and solutions\\nNutanix Data Services for Kubernetes (NDK)\\nNDK simplifies and unifies provisioning and operating cloud-native applications by extending enterprise data services to containerized apps.\\nNutanix Cloud Infrastructure (NCI):\\nNutanix Data Services for Kubernetes (NDK)\\nUse Cases:\\nCloud Native\\nFebruary 4, 2025\\nLearn more about NDK\\nNutanix Kubernetes Platform\\nNutanix Kubernetes Platform (NKP) simplifies platform engineering by reducing operational complexity and establishing consistency across any environment.\\nProducts:\\nNutanix Kubernetes Platform (NKP)\\nUse Cases:\\nCloud Native\\nFebruary 4, 2025\\nLearn more about NKP\\nSimplify Kubernetes Across Hybrid and Multicloud Environments\\nNKP speeds your Kubernetes journey with a single, centralized control point to run apps across distributed, diverse infrastructures.\\nProducts:\\nNutanix Kubernetes Platform (NKP)\\nUse Cases:\\nCloud Native\\nJuly 11, 2025\\nLearn more\\nLearn more about cloud native\\nCloud automation\\nCloud automation is the use of diverse tools and services by businesses to eliminate the laborious and time-consuming tasks associated with manually operating components of the cloud.\\nJanuary 29, 2024\\nLearn more\\nContainerization\\nDiscover the power of containerization with Nutanix. Learn how it streamlines deployment, enhances scalability, and boosts application efficiency.\\nAugust 8, 2024\\nLearn more\\nEdge computing\\nxplore edge computing with Nutanix. Learn what it is, how it works, benefits, challenges, and use cases.\\nUse Cases:\\nEdge and Remote Sites (ROBO)\\nJuly 15, 2025\\nLearn more\\nHybrid cloud\\nHybrid cloud computing combines on-premise IT with off-premise resources or services. Learn more about how hybrid cloud works and the benefits it can bring.\\nKey Play:\\nHybrid Cloud\\nUse Cases:\\nHybrid Multicloud\\nJuly 7, 2025\\nLearn more\\nKubernetes\\nLearn everything to know about Kubernetes, an open-source software for automating processes in deploying, scaling, and managing containerized applications.\\nJune 20, 2023\\nLearn more\\nMulticloud\\u00a0\\nMulticloud is the use of more than one cloud platform that delivers a specific application or service and can be comprised of public, private, and edge clouds.\\nKey Play:\\nHybrid Cloud\\nUse Cases:\\nHybrid Multicloud\\nSeptember 3, 2024\\nLearn more\\nWhat We Do\\nSolutions\\nProducts\\nResources\\nOur Customers\\nTech Terms\\nCompany\\nCareers\\nGlobal Offices\\nLeadership\\nNewsroom\\nInvestor Relations\\nSocial Responsibility\\nTrust\\nSupport\\nSupport Portal Login\\nContact Support\\nProduct Support\\nContact Us\\nPartner Login\\nBlog\\nThe Forecast\\nDeveloper Portal\\nExecutive Focus\\nEvents\\nWebinars on Demand\\n\\u00a9 Nutanix 2026\\nTerms of Use\\nPrivacy Statement\\nDo Not Sell or Share My Personal Information\\nTerms of Use\\nPrivacy Statement\\nDo Not Sell or Share My Personal Information\\n\"}"
},
"response": {
"status": "ok",
"response": [
"Nutanix offers cloud platform, central, prism, cloud infrastructure, disaster recovery, network security, cloud clusters, government cloud clusters, database service, Kubernetes platform, cloud manager, unified storage, data lens, and enterprise AI.",
"Key solutions include VMware alternative, hybrid cloud adoption, Kubernetes platform, business continuity, business-critical apps, cloud native, digital sovereignty, edge computing, hybrid multicloud, application migration, private cloud, security, sustainability, and databases.",
"Nutanix Kubernetes Platform (NKP) simplifies Kubernetes across hybrid and multicloud environments.",
"Cloud native applications prioritise speed, scalability, flexibility and resilience and are well suited for dynamic cloud environments such as public, private, or hybrid.",
"Cloud native applications use a modular architecture, microservices, Linux containers, and orchestration platforms like Kubernetes.",
"Cloud native applications use cases are E-commerce Platforms, Streaming Media Platforms, Live Chat Platforms, Digital Banking, Medical Imaging and Data Analytics Platform, Property Rental Platforms, Real-Time Data Analytics, Customized Consumer Recommendations, Automated Smart Home Systems and Location-Enabled Services Integration.",
"Cloud native applications can be deployed across different infrastructures.",
"DevOps and cloud native approach help IT teams to push frequent, reliable updates and manage application lifecycles seamlessly across hybrid and multicloud environments.",
"Key dates mentioned:",
"December 30, 2024",
"November 12, 2024",
"January 29, 2024",
"August 8, 2024",
"September 3, 2024",
"June 20, 2023",
"December 4, 2025",
"December 12, 2025",
"October 19, 2025",
"November 13, 2025",
"February 4, 2025",
"July 11, 2025",
"July 15, 2025",
"July 7, 2025",
"2026",
"Nutanix was named a leader in the Forrester Waveâ„¢: Multicloud Container Platforms, Q3 2025.",
"Nutanix was named a Challenger in the 2025 Gartner® Magic Quadrant™ for Container Management.",
"Nutanix was named a Leader in the 2025 Gartner® Magic Quadrant™ for Distributed Hybrid Infrastructure."
]
}
} {
"prompt": {
"label": "is_firewall",
"prompt": {
"prompt_id": "6",
"prompt_label": "is_firewall",
"content_format": "{\"data\":\"content\"}",
"success_format": "{\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"}",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON.\nIgnore cookie requests in your judgment.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: {\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"} Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON. Ignore cookie requests in your judgment."
},
"content": "{\"data\":\"could not scrap\\n\"}"
},
"response": {
"status": "ok",
"response": "true"
}
} {
"prompt": {
"label": "resume_data",
"prompt": {
"prompt_id": "7",
"prompt_label": "resume_data",
"content_format": "{\"data\":\"content\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you."
},
"content": "{\"data\":\"could not scrap\\n\"}"
},
"response": {
"status": "error",
"message": "Couldn't scrape any information, mate. Looks like there's nowt there to summarise."
}
} {
"prompt": {
"label": "resume_data",
"prompt": {
"prompt_id": "7",
"prompt_label": "resume_data",
"content_format": "{\"data\":\"content\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you."
},
"content": "{\"data\":\"could not scrap\\n\"}"
},
"response": {
"status": "error",
"message": "Right then, seems I've hit a snag, guv. Couldn't get my mitts on any actual content to summarise. Bit of a dead end, innit?"
}
} {
"prompt": {
"label": "resume_data",
"prompt": {
"prompt_id": "7",
"prompt_label": "resume_data",
"content_format": "{\"data\":\"content\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you."
},
"content": "{\"data\":\"could not scrap\\n\"}"
},
"response": {
"status": "error",
"message": "I'm ever so sorry, but I couldn't retrieve any information to summarise. It appears the content couldn't be scraped, so I'm afraid I've nothing to offer you at the moment, guv'nor."
}
} {
"prompt": {
"label": "is_firewall",
"prompt": {
"prompt_id": "6",
"prompt_label": "is_firewall",
"content_format": "{\"data\":\"content\"}",
"success_format": "{\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"}",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON.\nIgnore cookie requests in your judgment.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: {\"status\" : \"ok\",\"response\":\"true (firewall)/false (real content)\"} Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} You are an agent who detects whether the content provided to you seems to be from a website, an error message, or a security verification of a site or web server. If the content sent is \"could not scrap,\" return true in the JSON. Ignore cookie requests in your judgment."
},
"content": "{\"data\":\"Open menu\\nWebmail\\nNotifications\\nBack to menu\\nNo pending order\\nNo pending ticket\\nMy customer account\\nBack to menu\\nMy customer account\\nMy bills\\nMy products and services\\nMy payment methods\\nMy orders\\nMy contacts\\nMy support tickets\\nContact Sales\\nSupport\\nBack to menu\\nHelp center\\nSupport Levels\\nProfessional Services\\nCommunities\\nBack to menu\\nOVHcloud Community\\nOVHcloud Blog\\nEvents\\nLearn\\nBack to menu\\nDocumentation\\nTutorials\\nUse cases\\nDeveloper Centre\\nCompliance\\nCase Studies\\nVideos\\nStories\\nTraining\\nUnited Kingdom [\\u00a3]\\nBack to menu\\nEurope\\nDeutschland [\\u20ac]\\nEspa\\u00f1a [\\u20ac]\\nFrance [\\u20ac]\\nIreland [\\u20ac]\\nItalia [\\u20ac]\\nNederland [\\u20ac]\\nPolska [PLN]\\nPortugal [\\u20ac]\\nUnited Kingdom [\\u00a3]\\nAmerica\\nCanada (en) [$]\\nCanada (fr) [$]\\nUnited States [$]\\nAm\\u00e9rica Latina [$]\\nAfrica\\nMaroc [Dhs]\\nS\\u00e9n\\u00e9gal [FCFA]\\nTunisie [DT]\\nOceania\\nAustralia [A$]\\nAsia\\nSingapore [S$]\\nAsia [US$]\\nIndia [\\u20b9]\\nWorld\\nWorld [$]\\nWorld [\\u20ac]\\nOpen login menu\\nWelcome to OVHcloud.\\nLog in to order, manage your products and services, and track your orders.\\nMy customer account\\nWebmail\\nBare Metal & VPS\\nBack to menu\\nBare Metal & VPS\\nDedicated Servers\\nBack to menu\\nDedicated Servers\\nProducts\\nDiscover our dedicated servers\\nRise Servers\\nNew\\nThe most affordable bare-metal servers offered by OVHcloud.\\nAdvance Servers\\nNew\\nVersatile servers for small and medium businesses.\\nGame Servers\\nNew\\nFor video games and streaming platforms.\\nStorage Servers\\nServers for archiving, backup, and distributed storage.\\nScale Servers\\nNew\\nSpecifically designed for complex, high-resilience infrastructures.\\nHigh Grade Servers\\nThe most powerful servers, optimised for critical loads.\\nOperating systems and applications\\nOperating systems and applications adapted to your needs\\nDedicated server availability by region\\nThe availability of our servers in various regions around the world\\nBare Metal Wholesale\\nGet a full rack of Advance, Scale or High Grade servers.\\nUse Cases\\nAZ and resilience\\nGrid computing\\nSAP HANA\\nVirtualisation and containerisation\\nWebsite Business Application\\nHyperconverged Infrastructure\\nSoftware-defined Storage\\nBig Data and Analytics\\nArchiving and Backup\\nAI, Machine Learning & Deep Learning\\nConfidential Computing\\nDatabase\\nGaming\\nHigh Performance Computing\\nEco Dedicated Servers\\nBack to menu\\nEco Dedicated Servers\\nEco Dedicated Servers\\nExplore our Dedicated Servers\\nKimsufi Servers\\nLow-cost servers to get you started\\nSo you Start Servers\\nA range of dedicated servers that are perfect for startups and very small businesses\\nRise Servers\\nNew\\nTried-and-tested Intel and AMD platforms for competitive performance and price\\nOperating systems and distributions\\nFind the versions compatible with your Eco server\\nUse cases\\nWebsite and business application\\nEmail server\\nNew\\nData storage\\nNew\\nVirtual private servers \\u2013 VPS\\nBack to menu\\nVirtual private servers \\u2013 VPS\\nVirtual private servers \\u2013 VPS\\nVPS\\nNew\\nOur new VPS with maximum resources, the best prices, instant scalability, and reinforced security, available in all our regions.\\nDistributions and licences\\nSee all our distributions and licences available on VPS\\nOptions\\nCustomise your VPS with our advanced options\\nHelp\\nUse cases\\nAutomated workflows with n8n\\nNew\\nWordPress multisite platform\\nVideo game server\\nTest server with VPS\\nHosting trading applications on a Forex VPS\\nManaged Bare Metal\\nBack to menu\\nManaged Bare Metal\\nManaged Bare Metal\\nManaged Bare Metal Essentials powered by VMware\\u00ae\\nYour virtual infrastructure managed by OVHcloud\\nStorage and backups\\nBack to menu\\nStorage and backups\\nStorage and backup\\nExplore all our solutions\\nEnterprise File Storage\\nFully managed file storage based on NetApp ONTAP Select\\nHA-NAS\\nCentralised storage or backup space for your file data\\nCloud Disk Array\\nA scalable storage solution based on CEPH technology\\nVeeam Enterprise Plus\\nThe ultimate solution for protecting your data in a way that fits your needs\\nHYCU for OVHcloud\\nSimplify the backup and migration of your Nutanix workloads\\nUse cases\\nData storage for your Linux servers\\nData storage for your virtual machines\\nNetwork\\nBack to menu\\nNetwork\\nNetwork\\nAdditional IP\\nAssign and move dynamic IP addresses from one service to another\\nOVHcloud Load Balancer\\nBalance your application load across multiple backend servers\\nPrivate Network (vRack)\\nConnect all your OVHcloud services together with an isolated private network\\nOVHcloud Link Aggregation\\nGet a redundant, high-bandwith private network\\nOVHcloud Connect\\nConnect your datacentre to OVHcloud\\nPublic Bandwith\\nUpgrade your default guaranteed bandwidth\\nCDN Infrastructure\\nA dedicated CDN to complement your OVHcloud products\\nBring Your Own IP (BYOIP)\\nBring your IP addresses and simplify your migration to OVHcloud\\nNetwork Security\\nBack to menu\\nNetwork Security\\nNetwork Security\\nAnti DDoS infrastructure\\nKeep your infrastructures protected against DDoS attacks\\nGame DDoS Protection\\nProtect your gaming and e-sport business with best-in-class security solution\\nDNSSEC\\nProtect your data from DNS cache poisoning\\nSSL Gateway\\nSimplest way to enable security on your webpage. Without any effort!\\nIdentity, Security & Operations\\nBack to menu\\nIdentity, Security & Operations\\nIdentity, Security & Operations\\nIdentity and Access Management (IAM)\\nSecure your access management and enhance your productivity\\nLogs Data Platform\\nComplete platform to collect, store and view your logs\\nKey Management Service (KMS)\\nSecure your data across all your OVHcloud services from one central place\\nSecret Manager\\nProfessionally manage of all your secrets in one place\\nService Logs\\nMonitor your cloud environment\\u2019s performance and security\\nBare Metal Pod\\nBack to menu\\nBare Metal Pod\\nBare Metal Pod\\nSecNumCloud-qualified Bare Metal Pod\\nBare Metal performance in a SecNumCloud compliant sovereign environment.\\nUse Cases\\nData sovereignty\\nSecNumCloud-qualified solutions\\nDomain Hosting Email\\nBack to menu\\nDomain Hosting Email\\nDomain name\\nBack to menu\\nDomain name\\nDomain name\\nSearch for your domain name\\nTransfer your domain name to OVHcloud\\nRenew your domain name\\nSearch the secondary market (aftermarket)\\nQuick access\\nDomain name prices\\nWHOIS - Search for domain information\\nDNS server\\nSpecial offers\\nNew\\nWeb Hosting\\nBack to menu\\nWeb Hosting\\nWeb Hosting\\nAll Web packs\\nAdditional databases\\nSSL option\\nCDN option\\nQuick access\\nHow do I create a website?\\nHost your WordPress website\\nCreate your website in 1 click\\nCreate your online store\\nEmail & collaborative solutions\\nBack to menu\\nEmail & collaborative solutions\\nEmail & collaborative solutions\\nAll Email plans\\nAll Exchange plans\\nOffice 365 licences\\nSMS\\nBack to menu\\nSMS\\nSMS\\nSend your Pro text messages\\nPublic Cloud\\nBack to menu\\nPublic Cloud\\nPublic Cloud\\nBack to menu\\nPublic Cloud\\nPublic Cloud\\nDiscover Public Cloud\\nService ecosystem\\nAutomate your setup, propel your business\\nPricing\\nView our simple, accessible pricing\\nPublic Cloud free trial\\nTry out our solutions at no cost\\nSavings Plans\\nNew\\nOpt for a 1 to 36 month subscription and save on your Public Cloud resources.\\nThe advantages of the Public Cloud solution\\nDiscover cloud computing solutions to meet your needs\\nCloud Computing\\nFind out more about this growing practice\\nCertification & compliance\\nExplore how OVHcloud builds trusted solutions\\nTrusted Zones\\nDeploy your critical data in high-security zones\\nAvailability by region\\nExplore our catalogue coverage by region\\nLocal Zones\\nNew\\nDeploy cloud services closer to your users\\nOur documentation\\nRead our guides and tutorials\\nCompute\\nBack to menu\\nCompute\\nCompute\\nExplore all our Compute products\\nVirtual Machine Instances\\nGet versatile instances that can be adapted to suit all your needs.\\nCloud GPU\\nSpeed up your workloads with high-performance GPU instances.\\nMetal Instances\\nCombine the power of Bare Metal with cloud automation\\nOur documentation\\nBrowse our documentation for the Compute range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nLocal Zone\\nNew\\nDeploy cloud services closer to your users\\nStorage\\nBack to menu\\nStorage\\nStorage\\nExplore all our Storage products\\nBlock Storage\\nCreate storage volumes, which can be used as additional disks\\nObject Storage\\nGet S3-compatible unlimited storage on demand\\nCold Archive\\nHighly economical archiving for infrequently accessed data.\\nLocal Zone\\nNew\\nDeploy cloud services closer to your users\\nOur documentation\\nBrowse our documentation for the Storage range\\nNetwork\\nBack to menu\\nNetwork\\nNetwork\\nExplore all our Network products\\nPrivate Network\\nDeploy private networks via the OVHcloud vRack\\nLoad Balancer\\nManage variable traffic by spreading it across multiple resources\\nFloating IP\\nAssign and move your public IP from one service to another\\nGateway\\nManage a single connection point between your private network & internet\\nOur documentation\\nView our documentation for the Network range\\nContainers & Orchestration\\nBack to menu\\nContainers & Orchestration\\nContainers & Orchestration\\nExplore all our Containers & Orchestration products\\nManaged Kubernetes Service\\nOrchestrate your containerised applications with a CNCF-certified Kubernetes cluster\\nLoad Balancer for Managed Kubernetes Service\\nManage variations in activity by distributing traffic across multiple resources\\nManaged Rancher Service\\nNew\\nSimplified and centralised management of your Kubernetes clusters\\nManaged Private Registry\\nManage your images of containers and helmchart on a secure private registry\\nOur documentation\\nView our documentation for the Containers & Orchestration range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nDatabases\\nBack to menu\\nDatabases\\nDatabases\\nExplore all our Databases products\\nMongoDB\\nDocument-oriented NoSQL engine. Try for free with Free Tier\\nMySQL\\nPopular relational database that adapts to your usage\\nPostgreSQL\\nThe top open-source relational database engine\\nValkey\\nSmart in-memory storage\\nOur Documentation\\nView our documentation for the Databases range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nAnalytics\\nBack to menu\\nAnalytics\\nAnalytics\\nExplore all our Analytics products\\nKafka\\nQueueing solution for deploying your event-driven architectures\\nKafka Connect\\nExtension simplifying the ingestion of your sources to Apache Kafka\\nKafka MirrorMaker\\nReplication ensuring high availability for your Kafka clusters\\nLogs Data Platform\\nComplete platform to collect, store and view your logs\\nOpenSearch\\nA dedicated engine for indexing, searching and analyzing data\\nClickHouse\\nNew\\nUltra-fast data analysis at your fingertips\\nManaged Dashboards\\nGrafana platform for creating dashboards\\nOur documentation\\nView our documentation for the Analytics range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nData Platform\\nNew\\nBack to menu\\nData Platform\\nData Platform\\nBrowse all our Data Platform products\\nDiscover the OVHcloud Data Platform\\nNew\\nCarry out your Data & Analytics projects in record time and with ease\\nData Catalog\\nNew\\nMore than 50 connectors for all your data sources\\nLakehouse Manager\\nNew\\nUnified data warehouse and data lake storage, based on Apache Iceberg\\nData Processing Engine\\nNew\\nAutomate the execution and orchestration of your ETL\\/ELT workloads\\nAnalytics Manager\\nNew\\nCreate your dashboards and launch your requests with the Trino engine\\nApplication Services\\nNew\\nSDK and serverless services to deploy your APIs and Data applications\\nControl Center\\nNew\\nMonitor metrics, manage logs and alerts for your environments\\nAI & Machine Learning\\nBack to menu\\nAI & Machine Learning\\nAI & Machine Learning\\nExplore all our AI & Machine learning products\\nAI & Quantum Notebooks\\nLaunch your Jupyter or VS Code notebooks in the cloud, and choose from our native AI or quantum frameworks\\nAI Training\\nTrain your AI models\\nAI Deploy\\nDeploy machine learning models & get your predictions\\nAI Endpoints\\nNew\\nIntegrate generative AI models into your applications easily and securely via standard APIs.\\nOur documentation\\nBrowse our documentation for the AI & Machine Learning range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nQuantum Computing\\nBack to menu\\nQuantum Computing\\nQuantum Computing\\nExplore all our Quantum Computing products\\nQuantum Emulators\\nNew\\nSimulate your quantum algorithms on ready-to-use notebooks\\nQuantum Processing Units (QPU)\\nNew\\nAccess real quantum computers through our Quantum Platform\\nWhat is Quantum computing?\\nLearn more about the next accelerated computing revolution and how to develop today\\u2019s solutions with tomorrow\\u2019s quantum computers\\nIdentity, Security & Operations\\nBack to menu\\nIdentity, Security & Operations\\nIdentity, Security & Operations\\nDiscover all our Identity, Security & Operations products\\nIdentity and Access Management (IAM)\\nSecure your access management and improve your productivity\\nLogs Data Platform\\nComplete platform to collect, store and view your logs\\nKey Management Service (KMS)\\nSecure your data across all your OVHcloud services from one place\\nSecret Manager\\nProfessionally manage of all your secrets in one place\\nServices Logs\\nMonitor the performance and security of your cloud environment\\nHosted Private Cloud\\nBack to menu\\nHosted Private Cloud\\nVMware\\nBack to menu\\nVMware\\nVMware on OVHcloud\\nDiscover VMware on OVHcloud\\nPublic VCF as a Service\\nNew\\nShared and managed VMware solution, powered by VMware Cloud Foundation\\nManaged VMware vSphere solutions\\nManaged VMware solution for all enterprises\\nSecNumCloud-qualified Managed VMware vSphere\\nANSSI-qualified VMware Trusted Zone solution\\nSolutions\\nCompare VMware solutions\\nSAP on OVHcloud\\nDatacentre extension and migration\\nHybrid and Multi-Cloud Solutions\\nDisaster recovery solutions\\nEuropean Trusted Zone Solutions\\nView all solutions\\nNutanix\\nBack to menu\\nNutanix\\nHosted Private Cloud\\nNC2 on OVHcloud\\nNew\\nNutanix Cloud Clusters (NC2) on OVHcloud\\nNutanix on OVHcloud\\nOur scalable, ready-to-use Nutanix hyperconverged platform (HCI)\\nSecNumCloud-qualified Bare Metal Pod\\nNew\\nNutanix-certified servers available in SecNumCloud-qualified Bare Metal Pod\\nHYCU for OVHcloud\\nSimplify the backup and migration of your Nutanix workloads\\nVeeam Enterprise for all your backups\\nA dedicated Veeam Backup Replication solution for all your backups\\nUse cases\\nMigrate and manage your data\\nDisaster Recovery Plan (DRP)\\nHyperconvergence, savings and ecology\\nDisaster Recovery (DRaaS)\\nSAP HANA\\nBack to menu\\nSAP HANA\\nSAP HANA\\nSAP HANA on Private Cloud\\nThe solution that facilitates your SAP deployments in a sovereign cloud\\nSolutions\\nSAP on OVHcloud\\nOn-Prem Cloud Platform\\nBack to menu\\nOn-Prem Cloud Platform\\nOn-Prem Cloud Platform\\nOn-Prem Cloud Platform (OPCP)\\nOPCP enables you to deploy your services on-premises or at the edge, with complete autonomy and security. Air-gapped by design.\\nInfra as a Service\\nCore infrastructure to build and operate your on-premises cloud\\nPlatform as a Service\\nCloud-native environments and ready-to-use services\\nCloud ready\\nLanding Zone to deploy and manage workloads easily\\nStorage & Backup\\nBack to menu\\nStorage & Backup\\nStorage and backup\\nDiscover all the storage solutions\\nVeeam option for VMware backup\\nThe Veeam Managed Backup solution for backing up your virtual machines\\nZerto option for your VMware Disaster Recovery Plan\\nMulti-site Disaster Recovery Plan solution for your VMware clusters\\nVeeam option for Public VCF as a Service\\nA dedicated Veeam Backup Replication solution for all your backups\\nVeeam Enterprise - Licences\\nA dedicated Veeam Backup Replication solution for all your backups\\nHYCU for OVHcloud\\nSimplify the backup and migration of your Nutanix workloads\\nObject Storage\\nGet S3-compatible unlimited storage on demand\\nCold Archive\\nGet long-term archiving at the best price\\nNetApp - Enterprise File Storage\\nFully managed file storage based on NetApp ONTAP Select\\nUse cases\\nBackup and Disaster Recovery\\nBusiness continuity\\nDisaster Recovery for Managed VMware vSphere\\nDisaster Recovery for Nutanix on OVHcloud\\nNetwork\\nBack to menu\\nNetwork\\nNetwork\\nAdditional IP\\nAssign and move dynamic IP addresses from one service to another\\nOVHcloud Load Balancer\\nBalance your application load across multiple backend servers\\nPrivate Network (vRack)\\nConnect all your OVHcloud services together with an isolated private network\\nOVHcloud Connect\\nConnect your datacentre to OVHcloud\\nCDN Infrastructure\\nA dedicated CDN to complement your OVHcloud products\\nBring Your Own IP (BYOIP)\\nBring your IP addresses and simplify your migration to OVHcloud\\nNetwork Security\\nBack to menu\\nNetwork Security\\nNetwork Security\\nAnti-DDoS infrastructure\\nKeep your infrastructures protected against DDoS attacks\\nDNSSEC\\nProtect your data from DNS cache poisoning\\nSSL Gateway\\nSimplest way to enable security on your webpage. Without any effort!\\nIdentity, Security & Operations\\nBack to menu\\nIdentity, Security & Operations\\nIdentity, Security & Operations\\nIdentity and Access Management (IAM)\\nSecure your access management and enhance your productivity\\nLogs Data Platform\\nComplete platform to collect, store and view your logs\\nKey Management Service (KMS)\\nSecure your data across all your OVHcloud services from one central place\\nSecret Manager\\nProfessionally manage of all your secrets in one place\\nService Logs\\nMonitor your cloud environment\\u2019s performance and security\\nCompliance and certifications\\nBack to menu\\nCompliance and certifications\\nCompliance and certifications\\nFull list of standards and regulations\\nGDPR\\nCompliance with the General Data Protection Regulation (EU) 2016\\/679\\nSecNumCloud\\nANSSI Security Visa Qualification\\nHDS and healthcare data hosting\\nHosting healthcare data in the UK and across Europe\\nHIPAA and HITECH\\nHosting healthcare data in the US\\nPCI DSS\\nFinancial data hosting\\nISO\\/IEC 27001, 27017 and 27018\\nInformation Security Management\\nISO\\/IEC 27701\\nManaging the security of personal data processing\\nISO 14001\\nManaging environmental impacts\\nISO 50001\\nEnergy management\\nSOC 1, 2 and 3\\nAICPA SSAE 16\\/ISAE 3402 type II attestation and reports\\nEBA and ACPR\\nCompliance for financial services operators in Europe\\nG-Cloud\\nPublic sector cloud service delivery in the UK\\nSolutions\\nBack to menu\\nSolutions\\nUse Cases\\nBack to menu\\nUse Cases\\nUse Cases\\nMigrate to the cloud\\nHybrid cloud & Multi Cloud\\nApp Modernization\\nCloud Native App\\nArtificial Intelligence\\nBig Data Analytics\\nData Management\\nHigh-Performance Workloads\\nLarge Data set storage\\nGrid Computing\\nMove to PaaS\\nBackup and disaster recovery\\nBusiness Continuity\\nTrusted Zone\\nSecNumCloud Environment\\nNetwork Protection\\nCloud Security\\nExtension & Migration Datacenter\\nDatacenter transformation\\nElevate your brand reputation\\nPrioritise financial stability\\nProtect your business against cyberthreats\\nIndustry\\nBack to menu\\nIndustry\\nIndustry\\nPublic Sector\\nA trusted solution for governments and authorities\\nHealthcare\\nThe trusted solution for the healthcare sector\\nFinancial Service\\nOur solutions for financial services operators\\nManufacturing\\nThe trusted cloud solution for European manufacturers\\nSoftware\\/Information Technology\\nSaaS and PaaS solutions from OVHcloud Partner Software Publishers\\nGaming\\nCloud solutions for companies and individuals in the gaming industry\\nBlockchain\\nFree up your blockchain projects with OVHcloud solutions\\nOrganisation Type\\nBack to menu\\nOrganisation Type\\nOrganisation Type\\nEnterprise\\nSolutions for enterprise-level digital transformation\\nSoftware publishers (SaaS\\/PaaS)\\nSaaS and PaaS solutions from OVHcloud Partner Software Publishers\\nSystem Integrator\\nSolutions for integrators, service providers and consulting firms\\nGovernment \\/ Administrations\\nTrusted solutions for governments and authorities\\nStartup\\nSupport solutions for start-ups\\nScaleup\\nSupport solutions for scale-ups\\nTechnology\\nBack to menu\\nTechnology\\nTechnology\\nVeeam\\nProtect your data with Veeam solutions offered by OVHcloud\\nVMware by Broadcom\\nVMware by Broadcom and OVHcloud solutions for all your projects\\nNutanix\\nAccelerate and simplify your hybrid multicloud journey with Nutanix on OVHcloud solution\\nHYCU\\nThe backup solution trusted by Nutanix users\\nSAP\\nOur SAP on OVHcloud solutions for SAP environments hosting in a sovereign cloud\\nNetApp\\nNetApp storage solutions with cost control and high performance\\nNvidia\\nNvidia GPU solutions for accelerating your innovation and AI projects\\nMongoDB\\nMongoDB solutions that simplify data management\\nOpenStack\\nOpenStack solutions integrated with OVHcloud for cloud infrastructure\\nIntel\\nExpert solutions powered by Intel\\u00ae Xeon\\u00ae that accelerate cloud processes\\nAMD\\nTop-of-the-line cloud solutions powered by AMD processors\\nHadoop Cloudera\\nYour 100% managed Cloudera solution with Claranet\\nEcosystem\\nBack to menu\\nEcosystem\\nEcosystem\\nDiscover the OVHcloud partner ecosystem\\nPartner Program\\nAn initiative dedicated to our reseller partners, integrators, administrators and consultants.\\nOpen Trusted Cloud\\nAn ecosystem of labelled SaaS and PaaS solutions, hosted in our open, reversible and reliable cloud\\nStartup Program\\nA support program for startups and scaleups to accelerate their growth\\nOVHcloud Labs\\nThe innovation zone to test our cutting-edge technologies before they are officially launched on the market\\nOur Ecosystem events\\nFind all the events dedicated to our partner ecosystem: webinars, conferences, and more\\nOVHcloud Ecosystem Awards\\nDiscover our OVHcloud Ecosystem awards that rewards our ecosystem leaders of the Year per category\\nTraining & Certification\\nDevelop your expertise with the training and certifications available to OVHcloud Partner Program members.\\nQuick Access\\nFind a partner\\nSign up to the OVHcloud Partner Program\\nSign up to the OVHcloud Startup Program\\nPrice comparison\\nPartner Portal\\nFAQ Partner Program\\nAbout\\nBack to menu\\nAbout\\nAbout\\nWho we are\\nNewsroom\\nGlobal infrastructure\\nOur datacenters\\nOur Local Zones\\nBackbone network\\nJoin the OVHcloud adventure\\nPatent Pledge\\nLegal\\nGDPR - Personal data protection\\nOur commitments\\nInnovation\\nSustainable cloud\\nTrusted cloud\\nInvestor Relations\\nEnvironmental Impact Tracker\\nSummit\\nOpen search bar\\nClose search bar\\nNo result\\nProducts\\nSolutions\\nPartners\\nDocumentation\\nArticles\\nSee all results\\nWhat is Cloud Native ?\\nLearning Centre\\nWhat is Cloud Native ?\\nCloud native lets business construct, deploy and maintain applications in the cloud within a flexible architecture. Crucially, these apps allow enterprise to leverage the many advantages offered by cloud-based services including the flexibility, scalability and resilience needed to remain competitive in tough market conditions.\\nWhat does cloud native mean?\\nGoing cloud native is vital to modern organisations that want to introduce new functionality or services that take full advantage of the cloud\\u2019s elasticity and distributive potential to meet enterprise and client demands.\\n\\u2018Old school\\u2019 solution\\nCloud native development is now vital as traditional methods of software development can no longer cut it in our fast-moving world. For instance, software development has typically been based on the monolithic model; a single custom-designed and built \\u2018structure\\u2019 where each element \\u2013 for instance, scripts and processes \\u2013 are often dependent on one another.\\nThis means evolving, changing or updating a monolithic solution\\u2019s code requires time and caution. Think of a Jenga tower \\u2013 or tumbling tower blocks \\u2013\\u00a0where removing one piece to replace it with another represents a potential risk to the entire infrastructure. Remove too many and that tower will eventually tumble down, crippling the system.\\nIn real world terms, evolving monolithic software is now becoming too complex, challenging and costly \\u2013 and no longer practical within a modern, fast-moving organisation where any downtime can impact bottom lines and cause reputational damage.\\nCloud native vs monolithic\\nEnter cloud native, which takes the opposite approach to monolithic. Creating cloud-native apps sees each application divided into individual software services, called microservices. A microservice fulfils a particular function within the app \\u2013 think payment, search, display, etc.\\nImportantly, each can be managed individually and independently, meaning you don\\u2019t need to worry about negatively impacting on the underlying infrastructure. All in, cloud native technologies make it easier to provision scaled cloud native apps to several million users simultaneously, no matter where they are in the world.\\nHow are cloud native technologies delivered?\\nRunning behind the scenes, cloud-native application development services and cloud native platform give you the tools, model and infrastructure you need to develop, roll out and maintain cloud native apps. Example include:\\nMicroservices\\nThese form the beating heart of any cloud-native architecture with each microservice independently tackling a specific business function (payment, search, display, etc.). Developed autonomously, microservices offering different services are combined to create an app, connected to one another using an application programming interface. Crucially, developers can change a microservice within an application without needing to take the entire app offline. This means new functionality or maintenance\\/upgrade work can be carried out without disruption to the enterprise.\\nDevOps\\nCrucial to going cloud-native, this approach sees developers and IT operation teams working together, breaking down internal silos to create a single entity committed to improving application modernization outcomes. Successful DevOps achieve this by automating software creation and delivery processes as well as infrastructures, relying on each other as well as crucial cloud native technologies processes and resources such as continuous integration\\/continuous delivery.\\nContainer registry\\nContainer images are stored and managed within a container registry, which provides all vital details on the \\u2018contents\\u2019 of the container from versioning and access control through to metadata\\/tagging and the software components themselves. This registry is then used by the container orchestration platform to access the container. Popular container registry solutions include Docker Hub, Google Container Registry, Amazon Elastic Container Registry and Azure Container Registry.\\nContinuous integration\\/continuous delivery (CI\\/CD)\\nContinuous integration (CI) allows coders to make changes to existing code without worrying about testing as the CI runs automated testing processes. CI checks for bugs as well as ensuring any new code is compatible with existing coding. This gives devs far quicker feedback and reduces risks to the codebase. Continuous delivery also automates the deployment of new code into the existing codebase. Combined, these cloud native technologies enable changes to be made to cloud native apps at speed and at scale, delivering shortened release cycles and consistent, reliable results.\\nServerless computing\\nThis allows dev teams to move away from managing the logistics of environments and infrastructure such as provisioning or managing servers. Instead, they can focus on building and coding exclusively, allowing the cloud-native approach to take on the behind the scenes \\u2018busywork\\u2019 such as automating resources scaling. Such functionality offers a range of benefits. It makes work easier and, for the business, creates a more cost effective coding process as development is simplified, the use of resources massively optimised, and performance enhanced.\\nNotifications\\nDelivered via comms channels of your choice, notifications are generated in real time and sent to alert enterprise stakeholders about potential issues such as a failed deployment. They can also be leveraged to provide vital updates about account activity or any instances of high resource usage. Ultimately, notifications enable enterprise to monitor all cloud native apps, environments and infrastructure at a glance.\\nContainer orchestration platforms\\nA cloud native platform enables you to automate the scaling and management of applications that are containerised \\u2013 known as container images. Container images are made up of the executable software components, libraries, dependencies and more. These are used to create a cloud-native application, enabling you to pick up, move and run your code in any environment. Cloud native technologies represent the ultimate in portability \\u2013\\u00a0and are one of the core strengths of going native cloud.\\nTo orchestrate such potentially complex operations, leading container orchestration platforms like\\nKubernetes\\nare used to massively simplify the process so you can focus solely on exploiting the container\\u2019s components, no matter the environment. To achieve this, the platform gives your teams complete control over the containers, ensuring you know where and how they are executed at all times.\\nWhat is the difference between cloud and native cloud?\\nBoth are crucial to creating modern systems and applications. However, \\u2018cloud\\u2019 refers to\\ncloud computing\\n. The business pays a rolling fee to gain access to an on-demand service\\u00a0 including a remote data server, which gives you access to the computing resources needed to go cloud native.\\nSuch cloud native technologies combined with a cloud native platform enable you to build and deliver applications before deploying them in the cloud \\u2013\\u00a0or if preferred, transfer any cloud native apps into a hybrid cloud or on-premise only. To enjoy the best that cloud native has to offer, both cloud and cloud native are essential for businesses that want to put themselves in the best position to meet all their future computing needs.\\nWhat are the benefits of cloud native for business?\\nThe cloud-native approach has rapidly become the gold standard for developing modern applications and environments, delivering a range of significant benefits. Examples include:\\nDevelop without fear\\nCloud-native microservices can be added or updated independently and deployed without affecting the stability or availability of the cloud native app itself. This enables you to make improvements by iterating whenever required \\u2013 without ever posing a threat to your operations.\\nSecure business continuity\\nBusiness continuity is strengthened by a microservice-first architecture. For companies adopting a hybrid and multi-cloud strategy, the risk of prolonged downtime is also low, meaning back office as well as customer experiences remain far more protected.\\nReduce time to market\\nAs your needs evolve, your applications must be able to adapt to meet them. Going cloud native speeds up cloud native application development. Deploy upgrades without time-consuming steps \\u2013 such as configuration, standardisation, tests, additions, modifications, etc. \\u2013\\u00a0as these are now fully automated, reducing the time between design and production or the need for deep management.\\nBe truly independent\\nAny cloud-native approach is based on an ecosystem of open source, interoperable services that promote code portability from one service provider to another \\u2013 so long as your approach remains compliant with open source standards. This also removes the dangers of vendor lock-in, enabling you to maintain complete sovereignty over your infrastructure, cloud native apps and services.\\nLeverage budgets better\\nThanks to the time saved by cloud native, the costs of managing a traditional infrastructure can be allocated to other developments instead. Crucially, you no longer need to risk wasting provision resources as computing, network and storage resources are allocated dynamically to meet your real infrastructure needs.\\nBoost security levels\\nThe more attack surfaces you have, the more open to threat you are. Cloud-native applications boost security by minimising your attack surfaces while improving your ability to identify and address threats or vulnerabilities. Also, patching and updating is made more simple thanks to cloud-native\\u2019s standardised deployment and management.\\nIncrease resilience and availability\\nCloud-native design offers inherent infrastructure resilience and increased application availability, as well as the automation of environment deployments and their associated configurations. This makes it easier to establish update, production implementation and redundancy scenarios, and even develop a robust disaster recovery and data backup plan.\\nRemain compliant 24\\/7\\nBecause security controls for cloud native applications are administered at the platform level, the need \\u2013 and expense \\u2013 of meeting data compliance regulations is greatly reduced. Any reputable cloud provider will also have strict security processes in place to ensure risk management strategies meet all regulatory requirements.\\nOVHcloud and Cloud Native\\nWe offer a range of PaaS solutions to aid you go cloud native, allowing you to automatically orchestrate your containerised applications, accelerate your time-to-market and get access to a scalable infrastructure that allows any enterprise to outperform its competitors.\\nOrchestrate your containers\\nKubernetes\\nis one of the most widely-used container orchestration tools on the market, adopted by companies of all sizes. It can be utilised to deploy applications, scale them up and make them more resilient \\u2014 even within hybrid or multi-cloud infrastructures.\\nDiscover our Managed Kubernetes\\nAccelerate your time-to-market\\nWith our cloud native platform as a Service solution, you can automatically orchestrate your containerised applications, integrate your software factory deployments, and adopt Infrastructure as Code. Combined, they enable you to deploy a winning\\ncloud-native strategy\\nto help future proof your operations in an increasingly competitive market.\\nOur cloud native platform\\nScale your cloud-native application\\nGet an automated and scalable\\ncloud-native architecture\\nby discovering the power of automation on a full three-node Kubernetes cluster that leaves you free to focus on the software layers. To help you get started, use robust discovery instances for your first steps with Kubernetes and introduce more powerful instances at any time.\\nCloud-native architecture\\nBack to top\\nTools\\nMy customer account\\nWebmail\\nAPI\\nProcedure\\nMailing lists\\nStatus\\nWhois\\nDomain contact\\nReport abuse (abuse@ovh.net)\\nWHOIS information disclosure request\\nIntellectual property\\nTrademarks\\nSupport\\nHelp centre\\nGuides\\nLearning Centre\\nGlossary\\nCommunity\\nSupport levels\\nContact us\\nOVHcloud Customer Service\\nMonday to Friday, 9am to 6pm\\n+44333 370 0425\\nLocal call rate\\nNews\\nPress\\nBlog\\nSocial networks\\nKeep in touch\\n\\u00a9 Copyright 1999-2026 OVH SAS.\\nTerms & conditions\\nContracts\\nData protection\\nManage my cookies\\nRights and obligations of domain name holders\\nICANN documentation for domain name holders\\nPayments\\nSitemap\\nAbout OVHcloud\\nOVHcloud Careers\\nIn accordance with the 2006\\/112\\/CE Directive, modified on 01\\/01\\/2015, prices incl. VAT may vary according to the customer's country of residence\\n(by default, the prices displayed are inclusive of the UK VAT in force).\\n\"}"
},
"response": {
"status": "false",
"response": "false"
}
} {
"prompt": {
"label": "resume_data",
"prompt": {
"prompt_id": "7",
"prompt_label": "resume_data",
"content_format": "{\"data\":\"content\"}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} Summarize in English as a bullet-point list with simple words all the information and numerical data provided to you."
},
"content": "{\"data\":\"Open menu\\nWebmail\\nNotifications\\nBack to menu\\nNo pending order\\nNo pending ticket\\nMy customer account\\nBack to menu\\nMy customer account\\nMy bills\\nMy products and services\\nMy payment methods\\nMy orders\\nMy contacts\\nMy support tickets\\nContact Sales\\nSupport\\nBack to menu\\nHelp center\\nSupport Levels\\nProfessional Services\\nCommunities\\nBack to menu\\nOVHcloud Community\\nOVHcloud Blog\\nEvents\\nLearn\\nBack to menu\\nDocumentation\\nTutorials\\nUse cases\\nDeveloper Centre\\nCompliance\\nCase Studies\\nVideos\\nStories\\nTraining\\nUnited Kingdom [\\u00a3]\\nBack to menu\\nEurope\\nDeutschland [\\u20ac]\\nEspa\\u00f1a [\\u20ac]\\nFrance [\\u20ac]\\nIreland [\\u20ac]\\nItalia [\\u20ac]\\nNederland [\\u20ac]\\nPolska [PLN]\\nPortugal [\\u20ac]\\nUnited Kingdom [\\u00a3]\\nAmerica\\nCanada (en) [$]\\nCanada (fr) [$]\\nUnited States [$]\\nAm\\u00e9rica Latina [$]\\nAfrica\\nMaroc [Dhs]\\nS\\u00e9n\\u00e9gal [FCFA]\\nTunisie [DT]\\nOceania\\nAustralia [A$]\\nAsia\\nSingapore [S$]\\nAsia [US$]\\nIndia [\\u20b9]\\nWorld\\nWorld [$]\\nWorld [\\u20ac]\\nOpen login menu\\nWelcome to OVHcloud.\\nLog in to order, manage your products and services, and track your orders.\\nMy customer account\\nWebmail\\nBare Metal & VPS\\nBack to menu\\nBare Metal & VPS\\nDedicated Servers\\nBack to menu\\nDedicated Servers\\nProducts\\nDiscover our dedicated servers\\nRise Servers\\nNew\\nThe most affordable bare-metal servers offered by OVHcloud.\\nAdvance Servers\\nNew\\nVersatile servers for small and medium businesses.\\nGame Servers\\nNew\\nFor video games and streaming platforms.\\nStorage Servers\\nServers for archiving, backup, and distributed storage.\\nScale Servers\\nNew\\nSpecifically designed for complex, high-resilience infrastructures.\\nHigh Grade Servers\\nThe most powerful servers, optimised for critical loads.\\nOperating systems and applications\\nOperating systems and applications adapted to your needs\\nDedicated server availability by region\\nThe availability of our servers in various regions around the world\\nBare Metal Wholesale\\nGet a full rack of Advance, Scale or High Grade servers.\\nUse Cases\\nAZ and resilience\\nGrid computing\\nSAP HANA\\nVirtualisation and containerisation\\nWebsite Business Application\\nHyperconverged Infrastructure\\nSoftware-defined Storage\\nBig Data and Analytics\\nArchiving and Backup\\nAI, Machine Learning & Deep Learning\\nConfidential Computing\\nDatabase\\nGaming\\nHigh Performance Computing\\nEco Dedicated Servers\\nBack to menu\\nEco Dedicated Servers\\nEco Dedicated Servers\\nExplore our Dedicated Servers\\nKimsufi Servers\\nLow-cost servers to get you started\\nSo you Start Servers\\nA range of dedicated servers that are perfect for startups and very small businesses\\nRise Servers\\nNew\\nTried-and-tested Intel and AMD platforms for competitive performance and price\\nOperating systems and distributions\\nFind the versions compatible with your Eco server\\nUse cases\\nWebsite and business application\\nEmail server\\nNew\\nData storage\\nNew\\nVirtual private servers \\u2013 VPS\\nBack to menu\\nVirtual private servers \\u2013 VPS\\nVirtual private servers \\u2013 VPS\\nVPS\\nNew\\nOur new VPS with maximum resources, the best prices, instant scalability, and reinforced security, available in all our regions.\\nDistributions and licences\\nSee all our distributions and licences available on VPS\\nOptions\\nCustomise your VPS with our advanced options\\nHelp\\nUse cases\\nAutomated workflows with n8n\\nNew\\nWordPress multisite platform\\nVideo game server\\nTest server with VPS\\nHosting trading applications on a Forex VPS\\nManaged Bare Metal\\nBack to menu\\nManaged Bare Metal\\nManaged Bare Metal\\nManaged Bare Metal Essentials powered by VMware\\u00ae\\nYour virtual infrastructure managed by OVHcloud\\nStorage and backups\\nBack to menu\\nStorage and backups\\nStorage and backup\\nExplore all our solutions\\nEnterprise File Storage\\nFully managed file storage based on NetApp ONTAP Select\\nHA-NAS\\nCentralised storage or backup space for your file data\\nCloud Disk Array\\nA scalable storage solution based on CEPH technology\\nVeeam Enterprise Plus\\nThe ultimate solution for protecting your data in a way that fits your needs\\nHYCU for OVHcloud\\nSimplify the backup and migration of your Nutanix workloads\\nUse cases\\nData storage for your Linux servers\\nData storage for your virtual machines\\nNetwork\\nBack to menu\\nNetwork\\nNetwork\\nAdditional IP\\nAssign and move dynamic IP addresses from one service to another\\nOVHcloud Load Balancer\\nBalance your application load across multiple backend servers\\nPrivate Network (vRack)\\nConnect all your OVHcloud services together with an isolated private network\\nOVHcloud Link Aggregation\\nGet a redundant, high-bandwith private network\\nOVHcloud Connect\\nConnect your datacentre to OVHcloud\\nPublic Bandwith\\nUpgrade your default guaranteed bandwidth\\nCDN Infrastructure\\nA dedicated CDN to complement your OVHcloud products\\nBring Your Own IP (BYOIP)\\nBring your IP addresses and simplify your migration to OVHcloud\\nNetwork Security\\nBack to menu\\nNetwork Security\\nNetwork Security\\nAnti DDoS infrastructure\\nKeep your infrastructures protected against DDoS attacks\\nGame DDoS Protection\\nProtect your gaming and e-sport business with best-in-class security solution\\nDNSSEC\\nProtect your data from DNS cache poisoning\\nSSL Gateway\\nSimplest way to enable security on your webpage. Without any effort!\\nIdentity, Security & Operations\\nBack to menu\\nIdentity, Security & Operations\\nIdentity, Security & Operations\\nIdentity and Access Management (IAM)\\nSecure your access management and enhance your productivity\\nLogs Data Platform\\nComplete platform to collect, store and view your logs\\nKey Management Service (KMS)\\nSecure your data across all your OVHcloud services from one central place\\nSecret Manager\\nProfessionally manage of all your secrets in one place\\nService Logs\\nMonitor your cloud environment\\u2019s performance and security\\nBare Metal Pod\\nBack to menu\\nBare Metal Pod\\nBare Metal Pod\\nSecNumCloud-qualified Bare Metal Pod\\nBare Metal performance in a SecNumCloud compliant sovereign environment.\\nUse Cases\\nData sovereignty\\nSecNumCloud-qualified solutions\\nDomain Hosting Email\\nBack to menu\\nDomain Hosting Email\\nDomain name\\nBack to menu\\nDomain name\\nDomain name\\nSearch for your domain name\\nTransfer your domain name to OVHcloud\\nRenew your domain name\\nSearch the secondary market (aftermarket)\\nQuick access\\nDomain name prices\\nWHOIS - Search for domain information\\nDNS server\\nSpecial offers\\nNew\\nWeb Hosting\\nBack to menu\\nWeb Hosting\\nWeb Hosting\\nAll Web packs\\nAdditional databases\\nSSL option\\nCDN option\\nQuick access\\nHow do I create a website?\\nHost your WordPress website\\nCreate your website in 1 click\\nCreate your online store\\nEmail & collaborative solutions\\nBack to menu\\nEmail & collaborative solutions\\nEmail & collaborative solutions\\nAll Email plans\\nAll Exchange plans\\nOffice 365 licences\\nSMS\\nBack to menu\\nSMS\\nSMS\\nSend your Pro text messages\\nPublic Cloud\\nBack to menu\\nPublic Cloud\\nPublic Cloud\\nBack to menu\\nPublic Cloud\\nPublic Cloud\\nDiscover Public Cloud\\nService ecosystem\\nAutomate your setup, propel your business\\nPricing\\nView our simple, accessible pricing\\nPublic Cloud free trial\\nTry out our solutions at no cost\\nSavings Plans\\nNew\\nOpt for a 1 to 36 month subscription and save on your Public Cloud resources.\\nThe advantages of the Public Cloud solution\\nDiscover cloud computing solutions to meet your needs\\nCloud Computing\\nFind out more about this growing practice\\nCertification & compliance\\nExplore how OVHcloud builds trusted solutions\\nTrusted Zones\\nDeploy your critical data in high-security zones\\nAvailability by region\\nExplore our catalogue coverage by region\\nLocal Zones\\nNew\\nDeploy cloud services closer to your users\\nOur documentation\\nRead our guides and tutorials\\nCompute\\nBack to menu\\nCompute\\nCompute\\nExplore all our Compute products\\nVirtual Machine Instances\\nGet versatile instances that can be adapted to suit all your needs.\\nCloud GPU\\nSpeed up your workloads with high-performance GPU instances.\\nMetal Instances\\nCombine the power of Bare Metal with cloud automation\\nOur documentation\\nBrowse our documentation for the Compute range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nLocal Zone\\nNew\\nDeploy cloud services closer to your users\\nStorage\\nBack to menu\\nStorage\\nStorage\\nExplore all our Storage products\\nBlock Storage\\nCreate storage volumes, which can be used as additional disks\\nObject Storage\\nGet S3-compatible unlimited storage on demand\\nCold Archive\\nHighly economical archiving for infrequently accessed data.\\nLocal Zone\\nNew\\nDeploy cloud services closer to your users\\nOur documentation\\nBrowse our documentation for the Storage range\\nNetwork\\nBack to menu\\nNetwork\\nNetwork\\nExplore all our Network products\\nPrivate Network\\nDeploy private networks via the OVHcloud vRack\\nLoad Balancer\\nManage variable traffic by spreading it across multiple resources\\nFloating IP\\nAssign and move your public IP from one service to another\\nGateway\\nManage a single connection point between your private network & internet\\nOur documentation\\nView our documentation for the Network range\\nContainers & Orchestration\\nBack to menu\\nContainers & Orchestration\\nContainers & Orchestration\\nExplore all our Containers & Orchestration products\\nManaged Kubernetes Service\\nOrchestrate your containerised applications with a CNCF-certified Kubernetes cluster\\nLoad Balancer for Managed Kubernetes Service\\nManage variations in activity by distributing traffic across multiple resources\\nManaged Rancher Service\\nNew\\nSimplified and centralised management of your Kubernetes clusters\\nManaged Private Registry\\nManage your images of containers and helmchart on a secure private registry\\nOur documentation\\nView our documentation for the Containers & Orchestration range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nDatabases\\nBack to menu\\nDatabases\\nDatabases\\nExplore all our Databases products\\nMongoDB\\nDocument-oriented NoSQL engine. Try for free with Free Tier\\nMySQL\\nPopular relational database that adapts to your usage\\nPostgreSQL\\nThe top open-source relational database engine\\nValkey\\nSmart in-memory storage\\nOur Documentation\\nView our documentation for the Databases range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nAnalytics\\nBack to menu\\nAnalytics\\nAnalytics\\nExplore all our Analytics products\\nKafka\\nQueueing solution for deploying your event-driven architectures\\nKafka Connect\\nExtension simplifying the ingestion of your sources to Apache Kafka\\nKafka MirrorMaker\\nReplication ensuring high availability for your Kafka clusters\\nLogs Data Platform\\nComplete platform to collect, store and view your logs\\nOpenSearch\\nA dedicated engine for indexing, searching and analyzing data\\nClickHouse\\nNew\\nUltra-fast data analysis at your fingertips\\nManaged Dashboards\\nGrafana platform for creating dashboards\\nOur documentation\\nView our documentation for the Analytics range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nData Platform\\nNew\\nBack to menu\\nData Platform\\nData Platform\\nBrowse all our Data Platform products\\nDiscover the OVHcloud Data Platform\\nNew\\nCarry out your Data & Analytics projects in record time and with ease\\nData Catalog\\nNew\\nMore than 50 connectors for all your data sources\\nLakehouse Manager\\nNew\\nUnified data warehouse and data lake storage, based on Apache Iceberg\\nData Processing Engine\\nNew\\nAutomate the execution and orchestration of your ETL\\/ELT workloads\\nAnalytics Manager\\nNew\\nCreate your dashboards and launch your requests with the Trino engine\\nApplication Services\\nNew\\nSDK and serverless services to deploy your APIs and Data applications\\nControl Center\\nNew\\nMonitor metrics, manage logs and alerts for your environments\\nAI & Machine Learning\\nBack to menu\\nAI & Machine Learning\\nAI & Machine Learning\\nExplore all our AI & Machine learning products\\nAI & Quantum Notebooks\\nLaunch your Jupyter or VS Code notebooks in the cloud, and choose from our native AI or quantum frameworks\\nAI Training\\nTrain your AI models\\nAI Deploy\\nDeploy machine learning models & get your predictions\\nAI Endpoints\\nNew\\nIntegrate generative AI models into your applications easily and securely via standard APIs.\\nOur documentation\\nBrowse our documentation for the AI & Machine Learning range\\nEn route to PaaS\\nFocus on your applications & become more competitive\\nQuantum Computing\\nBack to menu\\nQuantum Computing\\nQuantum Computing\\nExplore all our Quantum Computing products\\nQuantum Emulators\\nNew\\nSimulate your quantum algorithms on ready-to-use notebooks\\nQuantum Processing Units (QPU)\\nNew\\nAccess real quantum computers through our Quantum Platform\\nWhat is Quantum computing?\\nLearn more about the next accelerated computing revolution and how to develop today\\u2019s solutions with tomorrow\\u2019s quantum computers\\nIdentity, Security & Operations\\nBack to menu\\nIdentity, Security & Operations\\nIdentity, Security & Operations\\nDiscover all our Identity, Security & Operations products\\nIdentity and Access Management (IAM)\\nSecure your access management and improve your productivity\\nLogs Data Platform\\nComplete platform to collect, store and view your logs\\nKey Management Service (KMS)\\nSecure your data across all your OVHcloud services from one place\\nSecret Manager\\nProfessionally manage of all your secrets in one place\\nServices Logs\\nMonitor the performance and security of your cloud environment\\nHosted Private Cloud\\nBack to menu\\nHosted Private Cloud\\nVMware\\nBack to menu\\nVMware\\nVMware on OVHcloud\\nDiscover VMware on OVHcloud\\nPublic VCF as a Service\\nNew\\nShared and managed VMware solution, powered by VMware Cloud Foundation\\nManaged VMware vSphere solutions\\nManaged VMware solution for all enterprises\\nSecNumCloud-qualified Managed VMware vSphere\\nANSSI-qualified VMware Trusted Zone solution\\nSolutions\\nCompare VMware solutions\\nSAP on OVHcloud\\nDatacentre extension and migration\\nHybrid and Multi-Cloud Solutions\\nDisaster recovery solutions\\nEuropean Trusted Zone Solutions\\nView all solutions\\nNutanix\\nBack to menu\\nNutanix\\nHosted Private Cloud\\nNC2 on OVHcloud\\nNew\\nNutanix Cloud Clusters (NC2) on OVHcloud\\nNutanix on OVHcloud\\nOur scalable, ready-to-use Nutanix hyperconverged platform (HCI)\\nSecNumCloud-qualified Bare Metal Pod\\nNew\\nNutanix-certified servers available in SecNumCloud-qualified Bare Metal Pod\\nHYCU for OVHcloud\\nSimplify the backup and migration of your Nutanix workloads\\nVeeam Enterprise for all your backups\\nA dedicated Veeam Backup Replication solution for all your backups\\nUse cases\\nMigrate and manage your data\\nDisaster Recovery Plan (DRP)\\nHyperconvergence, savings and ecology\\nDisaster Recovery (DRaaS)\\nSAP HANA\\nBack to menu\\nSAP HANA\\nSAP HANA\\nSAP HANA on Private Cloud\\nThe solution that facilitates your SAP deployments in a sovereign cloud\\nSolutions\\nSAP on OVHcloud\\nOn-Prem Cloud Platform\\nBack to menu\\nOn-Prem Cloud Platform\\nOn-Prem Cloud Platform\\nOn-Prem Cloud Platform (OPCP)\\nOPCP enables you to deploy your services on-premises or at the edge, with complete autonomy and security. Air-gapped by design.\\nInfra as a Service\\nCore infrastructure to build and operate your on-premises cloud\\nPlatform as a Service\\nCloud-native environments and ready-to-use services\\nCloud ready\\nLanding Zone to deploy and manage workloads easily\\nStorage & Backup\\nBack to menu\\nStorage & Backup\\nStorage and backup\\nDiscover all the storage solutions\\nVeeam option for VMware backup\\nThe Veeam Managed Backup solution for backing up your virtual machines\\nZerto option for your VMware Disaster Recovery Plan\\nMulti-site Disaster Recovery Plan solution for your VMware clusters\\nVeeam option for Public VCF as a Service\\nA dedicated Veeam Backup Replication solution for all your backups\\nVeeam Enterprise - Licences\\nA dedicated Veeam Backup Replication solution for all your backups\\nHYCU for OVHcloud\\nSimplify the backup and migration of your Nutanix workloads\\nObject Storage\\nGet S3-compatible unlimited storage on demand\\nCold Archive\\nGet long-term archiving at the best price\\nNetApp - Enterprise File Storage\\nFully managed file storage based on NetApp ONTAP Select\\nUse cases\\nBackup and Disaster Recovery\\nBusiness continuity\\nDisaster Recovery for Managed VMware vSphere\\nDisaster Recovery for Nutanix on OVHcloud\\nNetwork\\nBack to menu\\nNetwork\\nNetwork\\nAdditional IP\\nAssign and move dynamic IP addresses from one service to another\\nOVHcloud Load Balancer\\nBalance your application load across multiple backend servers\\nPrivate Network (vRack)\\nConnect all your OVHcloud services together with an isolated private network\\nOVHcloud Connect\\nConnect your datacentre to OVHcloud\\nCDN Infrastructure\\nA dedicated CDN to complement your OVHcloud products\\nBring Your Own IP (BYOIP)\\nBring your IP addresses and simplify your migration to OVHcloud\\nNetwork Security\\nBack to menu\\nNetwork Security\\nNetwork Security\\nAnti-DDoS infrastructure\\nKeep your infrastructures protected against DDoS attacks\\nDNSSEC\\nProtect your data from DNS cache poisoning\\nSSL Gateway\\nSimplest way to enable security on your webpage. Without any effort!\\nIdentity, Security & Operations\\nBack to menu\\nIdentity, Security & Operations\\nIdentity, Security & Operations\\nIdentity and Access Management (IAM)\\nSecure your access management and enhance your productivity\\nLogs Data Platform\\nComplete platform to collect, store and view your logs\\nKey Management Service (KMS)\\nSecure your data across all your OVHcloud services from one central place\\nSecret Manager\\nProfessionally manage of all your secrets in one place\\nService Logs\\nMonitor your cloud environment\\u2019s performance and security\\nCompliance and certifications\\nBack to menu\\nCompliance and certifications\\nCompliance and certifications\\nFull list of standards and regulations\\nGDPR\\nCompliance with the General Data Protection Regulation (EU) 2016\\/679\\nSecNumCloud\\nANSSI Security Visa Qualification\\nHDS and healthcare data hosting\\nHosting healthcare data in the UK and across Europe\\nHIPAA and HITECH\\nHosting healthcare data in the US\\nPCI DSS\\nFinancial data hosting\\nISO\\/IEC 27001, 27017 and 27018\\nInformation Security Management\\nISO\\/IEC 27701\\nManaging the security of personal data processing\\nISO 14001\\nManaging environmental impacts\\nISO 50001\\nEnergy management\\nSOC 1, 2 and 3\\nAICPA SSAE 16\\/ISAE 3402 type II attestation and reports\\nEBA and ACPR\\nCompliance for financial services operators in Europe\\nG-Cloud\\nPublic sector cloud service delivery in the UK\\nSolutions\\nBack to menu\\nSolutions\\nUse Cases\\nBack to menu\\nUse Cases\\nUse Cases\\nMigrate to the cloud\\nHybrid cloud & Multi Cloud\\nApp Modernization\\nCloud Native App\\nArtificial Intelligence\\nBig Data Analytics\\nData Management\\nHigh-Performance Workloads\\nLarge Data set storage\\nGrid Computing\\nMove to PaaS\\nBackup and disaster recovery\\nBusiness Continuity\\nTrusted Zone\\nSecNumCloud Environment\\nNetwork Protection\\nCloud Security\\nExtension & Migration Datacenter\\nDatacenter transformation\\nElevate your brand reputation\\nPrioritise financial stability\\nProtect your business against cyberthreats\\nIndustry\\nBack to menu\\nIndustry\\nIndustry\\nPublic Sector\\nA trusted solution for governments and authorities\\nHealthcare\\nThe trusted solution for the healthcare sector\\nFinancial Service\\nOur solutions for financial services operators\\nManufacturing\\nThe trusted cloud solution for European manufacturers\\nSoftware\\/Information Technology\\nSaaS and PaaS solutions from OVHcloud Partner Software Publishers\\nGaming\\nCloud solutions for companies and individuals in the gaming industry\\nBlockchain\\nFree up your blockchain projects with OVHcloud solutions\\nOrganisation Type\\nBack to menu\\nOrganisation Type\\nOrganisation Type\\nEnterprise\\nSolutions for enterprise-level digital transformation\\nSoftware publishers (SaaS\\/PaaS)\\nSaaS and PaaS solutions from OVHcloud Partner Software Publishers\\nSystem Integrator\\nSolutions for integrators, service providers and consulting firms\\nGovernment \\/ Administrations\\nTrusted solutions for governments and authorities\\nStartup\\nSupport solutions for start-ups\\nScaleup\\nSupport solutions for scale-ups\\nTechnology\\nBack to menu\\nTechnology\\nTechnology\\nVeeam\\nProtect your data with Veeam solutions offered by OVHcloud\\nVMware by Broadcom\\nVMware by Broadcom and OVHcloud solutions for all your projects\\nNutanix\\nAccelerate and simplify your hybrid multicloud journey with Nutanix on OVHcloud solution\\nHYCU\\nThe backup solution trusted by Nutanix users\\nSAP\\nOur SAP on OVHcloud solutions for SAP environments hosting in a sovereign cloud\\nNetApp\\nNetApp storage solutions with cost control and high performance\\nNvidia\\nNvidia GPU solutions for accelerating your innovation and AI projects\\nMongoDB\\nMongoDB solutions that simplify data management\\nOpenStack\\nOpenStack solutions integrated with OVHcloud for cloud infrastructure\\nIntel\\nExpert solutions powered by Intel\\u00ae Xeon\\u00ae that accelerate cloud processes\\nAMD\\nTop-of-the-line cloud solutions powered by AMD processors\\nHadoop Cloudera\\nYour 100% managed Cloudera solution with Claranet\\nEcosystem\\nBack to menu\\nEcosystem\\nEcosystem\\nDiscover the OVHcloud partner ecosystem\\nPartner Program\\nAn initiative dedicated to our reseller partners, integrators, administrators and consultants.\\nOpen Trusted Cloud\\nAn ecosystem of labelled SaaS and PaaS solutions, hosted in our open, reversible and reliable cloud\\nStartup Program\\nA support program for startups and scaleups to accelerate their growth\\nOVHcloud Labs\\nThe innovation zone to test our cutting-edge technologies before they are officially launched on the market\\nOur Ecosystem events\\nFind all the events dedicated to our partner ecosystem: webinars, conferences, and more\\nOVHcloud Ecosystem Awards\\nDiscover our OVHcloud Ecosystem awards that rewards our ecosystem leaders of the Year per category\\nTraining & Certification\\nDevelop your expertise with the training and certifications available to OVHcloud Partner Program members.\\nQuick Access\\nFind a partner\\nSign up to the OVHcloud Partner Program\\nSign up to the OVHcloud Startup Program\\nPrice comparison\\nPartner Portal\\nFAQ Partner Program\\nAbout\\nBack to menu\\nAbout\\nAbout\\nWho we are\\nNewsroom\\nGlobal infrastructure\\nOur datacenters\\nOur Local Zones\\nBackbone network\\nJoin the OVHcloud adventure\\nPatent Pledge\\nLegal\\nGDPR - Personal data protection\\nOur commitments\\nInnovation\\nSustainable cloud\\nTrusted cloud\\nInvestor Relations\\nEnvironmental Impact Tracker\\nSummit\\nOpen search bar\\nClose search bar\\nNo result\\nProducts\\nSolutions\\nPartners\\nDocumentation\\nArticles\\nSee all results\\nWhat is Cloud Native ?\\nLearning Centre\\nWhat is Cloud Native ?\\nCloud native lets business construct, deploy and maintain applications in the cloud within a flexible architecture. Crucially, these apps allow enterprise to leverage the many advantages offered by cloud-based services including the flexibility, scalability and resilience needed to remain competitive in tough market conditions.\\nWhat does cloud native mean?\\nGoing cloud native is vital to modern organisations that want to introduce new functionality or services that take full advantage of the cloud\\u2019s elasticity and distributive potential to meet enterprise and client demands.\\n\\u2018Old school\\u2019 solution\\nCloud native development is now vital as traditional methods of software development can no longer cut it in our fast-moving world. For instance, software development has typically been based on the monolithic model; a single custom-designed and built \\u2018structure\\u2019 where each element \\u2013 for instance, scripts and processes \\u2013 are often dependent on one another.\\nThis means evolving, changing or updating a monolithic solution\\u2019s code requires time and caution. Think of a Jenga tower \\u2013 or tumbling tower blocks \\u2013\\u00a0where removing one piece to replace it with another represents a potential risk to the entire infrastructure. Remove too many and that tower will eventually tumble down, crippling the system.\\nIn real world terms, evolving monolithic software is now becoming too complex, challenging and costly \\u2013 and no longer practical within a modern, fast-moving organisation where any downtime can impact bottom lines and cause reputational damage.\\nCloud native vs monolithic\\nEnter cloud native, which takes the opposite approach to monolithic. Creating cloud-native apps sees each application divided into individual software services, called microservices. A microservice fulfils a particular function within the app \\u2013 think payment, search, display, etc.\\nImportantly, each can be managed individually and independently, meaning you don\\u2019t need to worry about negatively impacting on the underlying infrastructure. All in, cloud native technologies make it easier to provision scaled cloud native apps to several million users simultaneously, no matter where they are in the world.\\nHow are cloud native technologies delivered?\\nRunning behind the scenes, cloud-native application development services and cloud native platform give you the tools, model and infrastructure you need to develop, roll out and maintain cloud native apps. Example include:\\nMicroservices\\nThese form the beating heart of any cloud-native architecture with each microservice independently tackling a specific business function (payment, search, display, etc.). Developed autonomously, microservices offering different services are combined to create an app, connected to one another using an application programming interface. Crucially, developers can change a microservice within an application without needing to take the entire app offline. This means new functionality or maintenance\\/upgrade work can be carried out without disruption to the enterprise.\\nDevOps\\nCrucial to going cloud-native, this approach sees developers and IT operation teams working together, breaking down internal silos to create a single entity committed to improving application modernization outcomes. Successful DevOps achieve this by automating software creation and delivery processes as well as infrastructures, relying on each other as well as crucial cloud native technologies processes and resources such as continuous integration\\/continuous delivery.\\nContainer registry\\nContainer images are stored and managed within a container registry, which provides all vital details on the \\u2018contents\\u2019 of the container from versioning and access control through to metadata\\/tagging and the software components themselves. This registry is then used by the container orchestration platform to access the container. Popular container registry solutions include Docker Hub, Google Container Registry, Amazon Elastic Container Registry and Azure Container Registry.\\nContinuous integration\\/continuous delivery (CI\\/CD)\\nContinuous integration (CI) allows coders to make changes to existing code without worrying about testing as the CI runs automated testing processes. CI checks for bugs as well as ensuring any new code is compatible with existing coding. This gives devs far quicker feedback and reduces risks to the codebase. Continuous delivery also automates the deployment of new code into the existing codebase. Combined, these cloud native technologies enable changes to be made to cloud native apps at speed and at scale, delivering shortened release cycles and consistent, reliable results.\\nServerless computing\\nThis allows dev teams to move away from managing the logistics of environments and infrastructure such as provisioning or managing servers. Instead, they can focus on building and coding exclusively, allowing the cloud-native approach to take on the behind the scenes \\u2018busywork\\u2019 such as automating resources scaling. Such functionality offers a range of benefits. It makes work easier and, for the business, creates a more cost effective coding process as development is simplified, the use of resources massively optimised, and performance enhanced.\\nNotifications\\nDelivered via comms channels of your choice, notifications are generated in real time and sent to alert enterprise stakeholders about potential issues such as a failed deployment. They can also be leveraged to provide vital updates about account activity or any instances of high resource usage. Ultimately, notifications enable enterprise to monitor all cloud native apps, environments and infrastructure at a glance.\\nContainer orchestration platforms\\nA cloud native platform enables you to automate the scaling and management of applications that are containerised \\u2013 known as container images. Container images are made up of the executable software components, libraries, dependencies and more. These are used to create a cloud-native application, enabling you to pick up, move and run your code in any environment. Cloud native technologies represent the ultimate in portability \\u2013\\u00a0and are one of the core strengths of going native cloud.\\nTo orchestrate such potentially complex operations, leading container orchestration platforms like\\nKubernetes\\nare used to massively simplify the process so you can focus solely on exploiting the container\\u2019s components, no matter the environment. To achieve this, the platform gives your teams complete control over the containers, ensuring you know where and how they are executed at all times.\\nWhat is the difference between cloud and native cloud?\\nBoth are crucial to creating modern systems and applications. However, \\u2018cloud\\u2019 refers to\\ncloud computing\\n. The business pays a rolling fee to gain access to an on-demand service\\u00a0 including a remote data server, which gives you access to the computing resources needed to go cloud native.\\nSuch cloud native technologies combined with a cloud native platform enable you to build and deliver applications before deploying them in the cloud \\u2013\\u00a0or if preferred, transfer any cloud native apps into a hybrid cloud or on-premise only. To enjoy the best that cloud native has to offer, both cloud and cloud native are essential for businesses that want to put themselves in the best position to meet all their future computing needs.\\nWhat are the benefits of cloud native for business?\\nThe cloud-native approach has rapidly become the gold standard for developing modern applications and environments, delivering a range of significant benefits. Examples include:\\nDevelop without fear\\nCloud-native microservices can be added or updated independently and deployed without affecting the stability or availability of the cloud native app itself. This enables you to make improvements by iterating whenever required \\u2013 without ever posing a threat to your operations.\\nSecure business continuity\\nBusiness continuity is strengthened by a microservice-first architecture. For companies adopting a hybrid and multi-cloud strategy, the risk of prolonged downtime is also low, meaning back office as well as customer experiences remain far more protected.\\nReduce time to market\\nAs your needs evolve, your applications must be able to adapt to meet them. Going cloud native speeds up cloud native application development. Deploy upgrades without time-consuming steps \\u2013 such as configuration, standardisation, tests, additions, modifications, etc. \\u2013\\u00a0as these are now fully automated, reducing the time between design and production or the need for deep management.\\nBe truly independent\\nAny cloud-native approach is based on an ecosystem of open source, interoperable services that promote code portability from one service provider to another \\u2013 so long as your approach remains compliant with open source standards. This also removes the dangers of vendor lock-in, enabling you to maintain complete sovereignty over your infrastructure, cloud native apps and services.\\nLeverage budgets better\\nThanks to the time saved by cloud native, the costs of managing a traditional infrastructure can be allocated to other developments instead. Crucially, you no longer need to risk wasting provision resources as computing, network and storage resources are allocated dynamically to meet your real infrastructure needs.\\nBoost security levels\\nThe more attack surfaces you have, the more open to threat you are. Cloud-native applications boost security by minimising your attack surfaces while improving your ability to identify and address threats or vulnerabilities. Also, patching and updating is made more simple thanks to cloud-native\\u2019s standardised deployment and management.\\nIncrease resilience and availability\\nCloud-native design offers inherent infrastructure resilience and increased application availability, as well as the automation of environment deployments and their associated configurations. This makes it easier to establish update, production implementation and redundancy scenarios, and even develop a robust disaster recovery and data backup plan.\\nRemain compliant 24\\/7\\nBecause security controls for cloud native applications are administered at the platform level, the need \\u2013 and expense \\u2013 of meeting data compliance regulations is greatly reduced. Any reputable cloud provider will also have strict security processes in place to ensure risk management strategies meet all regulatory requirements.\\nOVHcloud and Cloud Native\\nWe offer a range of PaaS solutions to aid you go cloud native, allowing you to automatically orchestrate your containerised applications, accelerate your time-to-market and get access to a scalable infrastructure that allows any enterprise to outperform its competitors.\\nOrchestrate your containers\\nKubernetes\\nis one of the most widely-used container orchestration tools on the market, adopted by companies of all sizes. It can be utilised to deploy applications, scale them up and make them more resilient \\u2014 even within hybrid or multi-cloud infrastructures.\\nDiscover our Managed Kubernetes\\nAccelerate your time-to-market\\nWith our cloud native platform as a Service solution, you can automatically orchestrate your containerised applications, integrate your software factory deployments, and adopt Infrastructure as Code. Combined, they enable you to deploy a winning\\ncloud-native strategy\\nto help future proof your operations in an increasingly competitive market.\\nOur cloud native platform\\nScale your cloud-native application\\nGet an automated and scalable\\ncloud-native architecture\\nby discovering the power of automation on a full three-node Kubernetes cluster that leaves you free to focus on the software layers. To help you get started, use robust discovery instances for your first steps with Kubernetes and introduce more powerful instances at any time.\\nCloud-native architecture\\nBack to top\\nTools\\nMy customer account\\nWebmail\\nAPI\\nProcedure\\nMailing lists\\nStatus\\nWhois\\nDomain contact\\nReport abuse (abuse@ovh.net)\\nWHOIS information disclosure request\\nIntellectual property\\nTrademarks\\nSupport\\nHelp centre\\nGuides\\nLearning Centre\\nGlossary\\nCommunity\\nSupport levels\\nContact us\\nOVHcloud Customer Service\\nMonday to Friday, 9am to 6pm\\n+44333 370 0425\\nLocal call rate\\nNews\\nPress\\nBlog\\nSocial networks\\nKeep in touch\\n\\u00a9 Copyright 1999-2026 OVH SAS.\\nTerms & conditions\\nContracts\\nData protection\\nManage my cookies\\nRights and obligations of domain name holders\\nICANN documentation for domain name holders\\nPayments\\nSitemap\\nAbout OVHcloud\\nOVHcloud Careers\\nIn accordance with the 2006\\/112\\/CE Directive, modified on 01\\/01\\/2015, prices incl. VAT may vary according to the customer's country of residence\\n(by default, the prices displayed are inclusive of the UK VAT in force).\\n\"}"
},
"response": {
"status": "ok",
"response": [
"OVHcloud is a company offering a variety of cloud services.",
"It provides web hosting, domain names, servers, storage, and more.",
"Services include Bare Metal & VPS, Public Cloud, Hosted Private Cloud, and On-Prem Cloud Platform.",
"OVHcloud offers different types of servers like Rise, Advance, Game, Storage, Scale and High Grade Servers.",
"They also have Eco Dedicated Servers including Kimsufi and So you Start Servers.",
"VPS (Virtual Private Servers) are available with scalability and security.",
"Storage solutions include Enterprise File Storage, HA-NAS, and Cloud Disk Array.",
"Network solutions such as Additional IP, Load Balancer, and Private Network (vRack) are offered.",
"Security features include Anti-DDoS infrastructure and DNSSEC.",
"OVHcloud provides Identity, Security & Operations tools like IAM and Logs Data Platform.",
"They offer Public Cloud services with options for compute, storage, network, containers, databases, analytics, and AI/Machine Learning.",
"Solutions are available for VMware, Nutanix and SAP HANA.",
"OVHcloud has a partner ecosystem and a startup program.",
"Support is available via help centre, guides, community, and customer service (+44333 370 0425, Monday to Friday, 9am to 6pm).",
"The company respects data protection regulations like GDPR.",
"OVH SAS Copyright 1999-2026.",
"Prices include UK VAT by default and may vary according to the customer's country of residence"
]
}
} {
"prompt": {
"label": "kw_semantic",
"prompt": {
"prompt_id": "10",
"prompt_label": "kw_semantic",
"content_format": "{\"data\":[\"list_1\"],[\"list_2\"], etc...}",
"success_format": "{ \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] }",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "We will provide you with data, and you must extract the most important semantic keywords.",
"model": "claude-sonnet-4-5-20250929",
"max_tokens": 4096,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":[\"list_1\"],[\"list_2\"], etc...} Response format in case of success: { \"status\" : \"ok\", \"response\": [\"data 1\", \"data 2\", \"data etc.\"] } Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} We will provide you with data, and you must extract the most important semantic keywords."
},
"content": "{\"data\":[\"Cloud native computing uses cloud platforms to design, create, deploy and run applications.\",\"Cloud native apps use microservices (small pieces of software) in containers on cloud servers.\",\"Microservices can be written, tested and deployed independently, making development faster.\",\"Defects can be fixed in one microservice without affecting the whole application.\",\"Overloaded microservices can be easily replicated to share the workload.\",\"Developers can use the best tools and languages for each microservice.\",\"Cloud Native Computing Foundation (CNCF) manages open standards for cloud native.\",\"Cloud native enables scalable applications in public, private and hybrid clouds.\",\"Containers hold microservices, and service meshes connect them.\",\"Immutable infrastructure means containers are replaced, not modified.\",\"Microservices communicate through well-defined protocols (APIs).\",\"Cloud native apps can run in any cloud architecture (public, private, hybrid or multicloud).\",\"DevOps teams use continuous integration (CI) and continuous delivery (CD).\",\"Kubernetes automates deployment and management of containerised microservices.\",\"Cloud native apps use resources better, reducing costs.\",\"Docker is a common container standard.\",\"Traditional apps are single codebases, updated by replacing the whole application.\",\"Key components of cloud native development include:\",\"Containers and containerisation for portable and rapid deployment\",\"Microservices architecture for flexibility and faster development\",\"Immutable infrastructure for consistency and easier rollbacks\",\"Infrastructure-as-code (IaC) for automated provisioning\",\"Automation and orchestration (e.g., Kubernetes) for scalability\",\"Observability and monitoring for insights into performance\",\"Resilience and self-healing for stability\",\"Benefits of cloud native:\",\"Scalability and flexibility to meet demand\",\"Agile development and faster time to market\",\"Cost efficiency through resource optimisation\",\"Enhanced reliability and high availability\",\"Seamless DevOps and CI\\/CD integration\",\"Standards-based portability to reduce vendor lock-in\",\"Integrated security at every layer\",\"Challenges of cloud native:\",\"Complexity, skills gaps and learning curve\",\"Need for cultural shift towards DevOps\",\"Security and compliance considerations\",\"Managing distributed systems\",\"Cost management\",\"Best practices:\",\"Adopt microservices architecture\",\"Standardise on containers\",\"Automate deployment and scaling\",\"Use infrastructure as code (IaC)\",\"Prioritise observability and monitoring\",\"Integrate security at every layer\",\"Optimise costs and resource utilisation\",\"Cloud native apps scale well and manage resources efficiently.\",\"Effective transition of existing apps can be achieved by rearchitecting monolithic applications by identifying code sections that can be split into microservices\",\"Cloud native apps offer consistent experience across different cloud environments.\",\"The CNCF promotes cloud native technologies, supporting standards like Docker and Kubernetes.\",\"Cloud refers to computing services hosted by providers; cloud native is a way of building apps using cloud resources.\",\"Sales contact number: +44 207 5626 823\",\"The document was written on October 8, 2025\",\"Right, here's a summary of that lot, in bullet points:\",\"\\u2022\\t**Calico Overview:** Calico provides networking, security, and observability for cloud-native environments like Kubernetes.\",\"\\u2022\\t**Products:** Includes Calico Open Source and commercial editions (Calico Cloud and Calico Enterprise).\",\"\\u2022\\t**Key Features of Cloud Native Applications:**\",\"\\t\\u25cb\\tMicroservices architecture (small, independent services).\",\"\\t\\u25cb\\tContainer orchestration (e.g., Kubernetes for managing containers).\",\"\\t\\u25cb\\tImmutable infrastructure (replacing entire infrastructure with new versions).\",\"\\t\\u25cb\\tAutomation (using DevOps and CI\\/CD practices).\",\"\\t\\u25cb\\tResilience (self-healing and automated failover).\",\"\\t\\u25cb\\tScalability (easily scale up or down based on demand).\",\"\\t\\u25cb\\tPortability (across different cloud providers).\",\"\\u2022\\t**Benefits of Cloud Native:** Faster development, increased agility, improved scalability, reduced costs, and enhanced innovation.\",\"\\u2022\\t**Principles of Cloud Native:**\",\"\\t\\u25cb\\tMicroservices architecture.\",\"\\t\\u25cb\\tContainerisation.\",\"\\t\\u25cb\\tDynamic orchestration.\",\"\\t\\u25cb\\tDeclarative APIs.\",\"\\t\\u25cb\\tAutomation (DevOps, CI\\/CD).\",\"\\t\\u25cb\\tResilience and observability.\",\"\\t\\u25cb\\tScalability and elasticity.\",\"\\t\\u25cb\\tPortability.\",\"\\u2022\\t**Pros of Cloud Native:** Scalability, resilience, faster delivery, portability, resource optimisation, and improved collaboration.\",\"\\u2022\\t**Cons of Cloud Native:** Complexity, steep learning curve, increased operational overhead, cost management difficulties, vendor lock-in risks, and security challenges.\",\"\\u2022\\t**Cloud Native vs. Cloud-Based:** Cloud-based applications are often legacy systems moved to the cloud, while cloud native applications are built specifically for the cloud.\",\"\\u2022\\t**Key Use Cases:**\",\"\\t\\u25cb\\tDevOps and CI\\/CD (automating software delivery).\",\"\\t\\u25cb\\tLegacy modernisation (migrating old applications to the cloud).\",\"\\t\\u25cb\\tService mesh and messaging (managing inter-service communication).\",\"\\t\\u25cb\\tMedia and streaming (dynamic scalability for media delivery).\",\"\\u2022\\t**Best Practices for Implementation:**\",\"\\t\\u25cb\\tDesign for resilience and failover.\",\"\\t\\u25cb\\tImplement DevSecOps (integrate security into DevOps).\",\"\\t\\u25cb\\tLeverage cloud load balancers and ingress controllers.\",\"\\t\\u25cb\\tUse GitOps practices (manage infrastructure as code).\",\"\\t\\u25cb\\tEnsure comprehensive monitoring.\",\"\\u2022\\t**HanseMerkur Case Study:** Used Calico to reduce overhead and meet ISO 27001 compliance.\",\"\\u2022\\t**Calico's Support:**\",\"\\t\\u25cb\\tNetworking: High-performance data planes, multi-cluster connectivity, ingress\\/egress gateways.\",\"\\t\\u25cb\\tSecurity: Fine-grained network policy control, microsegmentation, threat prevention, policy lifecycle management.\",\"\\t\\u25cb\\tObservability: Real-time service and threat graphs, deep protocol visibility, targeted troubleshooting, centralised monitoring.\",\"\\u2022\\t**Box Case Study:** Adopted Calico for zero-trust security and policy automation across multi-cluster environments.\",\"\\u2022\\t**Next Steps:** Enforcing workload isolation, integrating security policies, monitoring network traffic.\",\"\\u2022\\t**Project Calico:** Includes documentation, community resources, and GitHub repository.\",\"**Cloud Native:**\",\" * It's a software development approach for building applications in cloud environments.\",\" * It uses containers, microservices, and orchestration.\",\" * It helps with scalability and resilience.\",\"**Key Concepts of Cloud Native Architecture**\",\" * Microservices: Individual components communicating via APIs.\",\" * Containers: Lightweight packages for deploying software.\",\" * DevOps: Automating building, testing, and deployment.\",\" * Immutable Infrastructure: Infrastructure that cannot be changed after being deployed.\",\" * Scalability and Elasticity: Ability to handle increasing work and adjust resources.\",\" * Service Mesh: Manages service-to-service communication.\",\" * Serverless Computing: Run apps without infrastructure management.\",\"**Benefits of Cloud Native:**\",\" * Faster time to market and agility.\",\" * Cost efficiency.\",\" * Better scalability and resilience.\",\" * Improved developer productivity and collaboration.\",\" * Security and compliance.\",\"**Challenges of Cloud Native:**\",\" * Cultural shifts required.\",\" * Technical complexity.\",\" * Security concerns.\",\" * Vendor lock-in.\",\" * Monitoring and observability difficulties.\",\"**How to Implement Cloud Native:**\",\" * Assess your current state.\",\" * Develop a strategy.\",\" * Use the right tools and infrastructure.\",\" * Follow best practices (e.g., use microservices, containers, automate releases).\",\"**Cloud Native vs. Cloud:**\",\" * Cloud refers to remote servers for data.\",\" * Cloud native refers to applications designed for cloud environments.\",\"**Cloud Native vs. Cloud Agnostic:**\",\" * Cloud Native apps are built for a specific cloud platform\",\" * Cloud Agnostic apps can run on any cloud platform.\",\"**Cloud Native vs. SaaS:**\",\" * Cloud native involves running your own cloud-designed applications.\",\" * SaaS means using third-party applications on the cloud for a subscription fee.\",\"**Cloud Providers:**\",\" * Amazon Web Services, Microsoft Azure, Google Cloud Platform, etc.\",\"**Popular Tools\\/Frameworks:**\",\" * Docker, Kubernetes, Prometheus, Envoy.\",\"Key solutions include VMware alternative, hybrid cloud adoption, Kubernetes platform, business continuity, business-critical apps, cloud native, digital sovereignty, edge computing, hybrid multicloud, application migration, private cloud, security, sustainability, and databases.\",\"Cloud native applications prioritise speed, scalability, flexibility and resilience and are well suited for dynamic cloud environments such as public, private, or hybrid.\",\"Cloud native applications use a modular architecture, microservices, Linux containers, and orchestration platforms like Kubernetes.\",\"Cloud native applications use cases are E-commerce Platforms, Streaming Media Platforms, Live Chat Platforms, Digital Banking, Medical Imaging and Data Analytics Platform, Property Rental Platforms, Real-Time Data Analytics, Customized Consumer Recommendations, Automated Smart Home Systems and Location-Enabled Services Integration.\",\"Cloud native applications can be deployed across different infrastructures.\",\"DevOps and cloud native approach help IT teams to push frequent, reliable updates and manage application lifecycles seamlessly across hybrid and multicloud environments.\",\"Key dates mentioned:\",\"December 30, 2024\",\"November 12, 2024\",\"January 29, 2024\",\"August 8, 2024\",\"September 3, 2024\",\"June 20, 2023\",\"December 4, 2025\",\"December 12, 2025\",\"October 19, 2025\",\"November 13, 2025\",\"February 4, 2025\",\"July 11, 2025\",\"July 15, 2025\",\"July 7, 2025\",\"2026\",\"OVHcloud is a company offering a variety of cloud services.\",\"It provides web hosting, domain names, servers, storage, and more.\",\"Services include Bare Metal & VPS, Public Cloud, Hosted Private Cloud, and On-Prem Cloud Platform.\",\"OVHcloud offers different types of servers like Rise, Advance, Game, Storage, Scale and High Grade Servers.\",\"They also have Eco Dedicated Servers including Kimsufi and So you Start Servers.\",\"VPS (Virtual Private Servers) are available with scalability and security.\",\"Storage solutions include Enterprise File Storage, HA-NAS, and Cloud Disk Array.\",\"Network solutions such as Additional IP, Load Balancer, and Private Network (vRack) are offered.\",\"Security features include Anti-DDoS infrastructure and DNSSEC.\",\"OVHcloud provides Identity, Security & Operations tools like IAM and Logs Data Platform.\",\"They offer Public Cloud services with options for compute, storage, network, containers, databases, analytics, and AI\\/Machine Learning.\",\"Solutions are available for VMware, Nutanix and SAP HANA.\",\"OVHcloud has a partner ecosystem and a startup program.\",\"Support is available via help centre, guides, community, and customer service (+44333 370 0425, Monday to Friday, 9am to 6pm).\",\"The company respects data protection regulations like GDPR.\",\"OVH SAS Copyright 1999-2026.\",\"Prices include UK VAT by default and may vary according to the customer's country of residence\"]}"
},
"response": {
"status": "ok",
"response": [
"cloud native computing",
"microservices architecture",
"containers",
"containerisation",
"Kubernetes",
"orchestration",
"scalability",
"DevOps",
"continuous integration",
"continuous delivery",
"CI/CD",
"Docker",
"Cloud Native Computing Foundation",
"CNCF",
"infrastructure as code",
"IaC",
"immutable infrastructure",
"service mesh",
"APIs",
"hybrid cloud",
"multicloud",
"public cloud",
"private cloud",
"automation",
"resilience",
"self-healing",
"observability",
"monitoring",
"portability",
"agility",
"cost efficiency",
"resource optimisation",
"security",
"compliance",
"DevSecOps",
"vendor lock-in",
"elasticity",
"declarative APIs",
"dynamic orchestration",
"cloud platforms",
"serverless computing",
"distributed systems",
"GitOps",
"load balancers",
"ingress controllers",
"microsegmentation",
"zero-trust security",
"network policy",
"threat prevention",
"Calico",
"Prometheus",
"Envoy",
"legacy modernisation",
"rearchitecting",
"monolithic applications",
"workload isolation",
"high availability",
"failover",
"cloud agnostic",
"SaaS",
"Amazon Web Services",
"Microsoft Azure",
"Google Cloud Platform",
"OVHcloud",
"VMware",
"Nutanix",
"edge computing",
"digital sovereignty",
"application migration",
"databases",
"streaming media",
"e-commerce",
"digital banking",
"data analytics",
"real-time processing"
]
}
} {
"prompt": {
"label": "is_right_lang",
"prompt": {
"prompt_id": "15",
"prompt_label": "is_right_lang",
"content_format": "{\"data\":\"content\"}",
"success_format": "{\"status\":\"ok\",\"response\":\"true/false\"}",
"error_format": "{\"status\":\"error\",\"message\":\"error message\"}",
"ban_words": "0",
"prompt_content": "We will give you a text, and you must say if the language of the data within the html is in English.",
"model": "gemini-2.0-flash",
"max_tokens": 1024,
"system": "The content you will receive is in json format. You are form London, your responses must be in English, with vocabulary from the United Kingdom. The response should be in json format. Do not return a linguistic consistency error Content format in json: {\"data\":\"content\"} Response format in case of success: {\"status\":\"ok\",\"response\":\"true/false\"} Response format in case of error: {\"status\":\"error\",\"message\":\"error message\"} We will give you a text, and you must say if the language of the data within the html is in English."
},
"content": "{\"data\":\"<p>Modern businesses are increasingly looking to harness the power of the cloud, and understanding what cloud native truly means has become essential for organisations seeking competitive advantages. This approach fundamentally changes how applications are designed, developed, and deployed, enabling companies to fully exploit the dynamic capabilities of cloud computing rather than simply migrating existing systems into a hosted environment.<\\/p><h2>What Cloud Native Really Means for Modern Applications<\\/h2><h3>Defining Cloud Native Architecture and Its Core Principles<\\/h3><p>Cloud native computing represents a comprehensive methodology for building and running applications that fully embrace the cloud computing model. At its heart, this approach relies on several foundational principles that distinguish it from traditional software development. The architecture centres on microservices, which are small, independent pieces of software that can be written, tested, and deployed separately from one another. These microservices reside within containers, lightweight packages that bundle all necessary dependencies, ensuring consistent operation across different environments. Orchestration platforms such as Kubernetes automate the deployment, scaling, and management of these containerised services, creating a dynamic system that responds intelligently to changing demands.<\\/p><p>The Cloud Native Computing Foundation plays a pivotal role in establishing and promoting open standards across the industry, supporting widely adopted technologies like Docker for containerisation and Kubernetes for orchestration. Get details on how these standards enable organisations to build applications that are inherently scalable, portable, and resilient. The immutable infrastructure principle ensures that containers are replaced rather than modified when updates occur, which maintains consistency and simplifies rollback procedures when issues arise. Communication between microservices happens through well-defined protocols known as APIs, creating a flexible ecosystem where each component can evolve independently without disrupting the broader application.<\\/p><h3>How Cloud Native Differs from Traditional Application Deployment<\\/h3><p>Traditional applications typically consist of monolithic codebases where all functionality is tightly integrated into a single unit. When updates are required, the entire application must be replaced or taken offline, creating downtime and limiting agility. Cloud native applications break this paradigm entirely by decomposing functionality into discrete microservices that can be updated, scaled, or replaced individually. This architectural shift means that defects can be fixed in one microservice without affecting the whole application, and overloaded services can be easily replicated to share the workload during periods of high demand.<\\/p><p>Another critical distinction lies in how resources are managed. Traditional deployments often involve static infrastructure that requires manual configuration and adjustment, whereas cloud native environments leverage infrastructure as code to automate provisioning and management. This declarative approach ensures that infrastructure states are version-controlled and reproducible, reducing the risk of configuration drift and human error. Cloud native applications can run seamlessly across public, private, hybrid, or multicloud architectures, offering organisations flexibility in choosing environments that best suit their security, compliance, and performance requirements.<\\/p><h2>The Business Advantages of Adopting Cloud Native Technologies<\\/h2><h3>Accelerated Development Cycles and Faster Time to Market<\\/h3><p>One of the most compelling business benefits of cloud native adoption is the dramatic acceleration of development cycles. Because microservices can be developed and deployed independently, development teams can work in parallel without waiting for other components to be completed. This parallelisation significantly reduces time to market, enabling organisations to respond swiftly to customer needs and competitive pressures. The integration of DevOps practices, particularly continuous integration and continuous delivery, creates automated pipelines that streamline the journey from code commit to production deployment.<\\/p><p>This agility extends beyond initial releases, as cloud native architectures facilitate rapid iteration and experimentation. Organisations can test new features with subsets of users, gather feedback, and make adjustments without the risk and complexity associated with traditional full-scale deployments. The ability to release updates frequently and reliably transforms how businesses innovate, allowing them to adapt strategies based on real-world usage patterns and emerging market trends. This responsiveness has become a critical differentiator in industries where customer expectations evolve rapidly, such as e-commerce platforms, streaming media services, and digital banking.<\\/p><h3>Enhanced Scalability and Cost Efficiency in Cloud Environments<\\/h3><p>Cloud native applications excel at managing resources efficiently, which translates directly into cost savings and operational flexibility. The elasticity inherent in cloud native design allows applications to scale up automatically when demand increases and scale down when traffic subsides, ensuring that organisations pay only for the resources they actually use. This dynamic resource allocation contrasts sharply with traditional infrastructure, where capacity must be provisioned for peak loads and often sits idle during quieter periods.<\\/p><p>Beyond simple cost reduction, cloud native architectures improve reliability and high availability by incorporating self-healing mechanisms and automated failover capabilities. When a container fails, orchestration platforms like Kubernetes automatically restart it or spin up a replacement, minimising downtime and maintaining service continuity. Observability and monitoring tools provide real-time insights into application performance, enabling teams to identify and address issues before they impact users. These capabilities are particularly valuable for business-critical applications in sectors such as medical imaging, data analytics platforms, and location-enabled services integration, where uptime and performance directly affect user experience and business outcomes.<\\/p><h2>Essential Cloud Native Practices: Containers and Microservices<\\/h2><h3>Leveraging Containerisation for Application Portability<\\/h3><p>Containerisation has become a cornerstone of cloud native development, providing a standardised way to package applications and their dependencies into portable units. Docker has emerged as the most widely adopted container standard, enabling developers to create consistent environments that run identically across development, testing, and production systems. This consistency eliminates the common challenge of applications behaving differently in various environments, often summarised as the problem of works on my machine syndrome.<\\/p><p>The portability that containers provide extends across cloud platforms, reducing vendor lock-in and enabling organisations to adopt multicloud or hybrid cloud strategies with confidence. Applications can be moved between Amazon Web Services, Microsoft Azure, Google Cloud Platform, and providers like OVHcloud without significant rearchitecting, preserving investment in development and maintaining operational flexibility. This cloud-agnostic capability is increasingly important as organisations seek to balance performance, cost, compliance, and data sovereignty requirements across different jurisdictions and regulatory environments.<\\/p><h3>Breaking Down Monoliths with Microservices Architecture<\\/h3><p>Transitioning from monolithic applications to microservices architecture represents a fundamental shift in how software is conceptualised and built. This process, often called legacy modernisation, involves identifying sections of existing codebases that can be extracted and reimplemented as independent services. Each microservice becomes responsible for a specific business capability, communicating with other services through well-defined APIs. This modular approach offers tremendous flexibility, as developers can choose the best programming languages, frameworks, and data storage technologies for each service rather than being constrained by a single technology stack.<\\/p><p>Microservices architecture also enables more effective workload isolation and resource management. Service meshes provide sophisticated capabilities for managing inter-service communication, including load balancing, traffic routing, and failure recovery. Technologies such as Envoy act as intelligent proxies that handle these concerns transparently, allowing developers to focus on business logic rather than infrastructure complexities. This separation of concerns improves both development velocity and operational resilience, making microservices an attractive choice for organisations building everything from live chat platforms to automated smart home systems.<\\/p><h2>DevOps and Automation: The Foundation of Cloud Native Success<\\/h2><h3>Implementing Continuous Integration and Continuous Deployment<\\/h3><p>DevOps practices form the cultural and technical foundation upon which cloud native success is built. Continuous integration ensures that code changes from multiple developers are merged and tested frequently, catching integration issues early when they are easier and less expensive to fix. Continuous deployment extends this principle by automating the release process, pushing tested changes into production environments without manual intervention. This automation reduces the risk of human error and enables organisations to release updates multiple times per day rather than in infrequent, high-risk big-bang releases.<\\/p><p>The integration of security into DevOps, known as DevSecOps, ensures that security considerations are addressed throughout the development lifecycle rather than as an afterthought. This includes automated security scanning of container images, enforcement of network policies, and implementation of zero-trust security models that verify every access request regardless of origin. Companies such as those adopting GitOps practices use version-controlled repositories as the single source of truth for both application code and infrastructure definitions, creating an auditable trail of changes and enabling rapid rollback when issues occur. These practices are particularly crucial for organisations operating in regulated industries where compliance requirements demand rigorous controls and documentation.<\\/p><h3>Automating Infrastructure Management for Improved Resilience<\\/h3><p>Infrastructure as code has transformed how organisations provision and manage computing resources, replacing manual configuration with declarative specifications that can be version-controlled and automatically applied. This approach ensures consistency across environments and makes infrastructure reproducible, addressing one of the most common sources of operational problems. Cloud native platforms handle dynamic orchestration, automatically distributing workloads across available resources and rebalancing them as conditions change.<\\/p><p>Automation extends to monitoring and observability, where tools like Prometheus collect metrics from distributed systems and provide insights into performance characteristics and potential issues. Real-time service graphs and deep protocol visibility enable teams to understand complex interactions between microservices, supporting targeted troubleshooting and capacity planning. Companies like Box have adopted comprehensive security and network policies managed through platforms such as Calico, achieving fine-grained control over traffic flows and implementing microsegmentation to limit the potential impact of security breaches. Similarly, organisations like HanseMerkur have leveraged cloud native tooling to meet stringent compliance standards including ISO 27001 whilst reducing operational overhead. These capabilities create self-healing systems that maintain stability even as individual components fail, embodying the resilience that makes cloud native architectures attractive for property rental platforms, customised consumer recommendations, and real-time processing applications where downtime directly impacts revenue and customer satisfaction.<\\/p>\"}"
},
"response": {
"status": "ok",
"response": "true"
}
}