Use Flow Repeater Component To Collect Information And Create Records | Summer 24 Release Feature

Use Flow Repeater Component To Collect Information And Create Records | Summer 24 Release Feature

Sudipta Deb

Sudipta Deb

Founder of Technical Potpourri, Co-Founder of Shrey Tech, Enterprise Cloud Architect

Welcome, Trailblazers! With each new Salesforce release comes a wave of innovation, empowering businesses and admins to unlock new capabilities and enhance user experiences. Among the exciting features introduced in the Summer '24 release is the groundbreaking Flow Repeater Component, designed to revolutionize the way users collect input and build lists of records seamlessly within Salesforce Flow.

In this blog post, I will delve into the intricacies of this game-changing feature, exploring how it simplifies the process of gathering user input to construct lists of records with unparalleled efficiency.

Watch The Video Or Read The Article (or do Both)

The form you have selected does not exist.

Use Case

Today I will be building a Screen Flow. I will be using the new Flow Component - Repeater to collect contact information and finally create all the contacts under the selected Account.

Step 1 - Fetch All Active Accounts

I will be using the Get Records element to fetch all active accounts from the org. I will be using the filter Active = True and select the option "All Records".

Step 2 - DataTable to Display All Accounts

Next, I will be using the Screen element and inside the Screen element, I will be adding the Datatable to display all the accounts I fetched in the previous steps. Here are the configuration for the datatable -

  • Source Collection - {!Get_All_Accounts}
  • Row Selection Mode - Single
  • Configure Rows - Account Number and Account Name

Step 3 - Repeater Component To Collect Contact Information

Here in this step, I will be adding the Repeater Component below the datatable to collect all Contact's information. Inside Repeater Component, I will be adding below elements -

  • Text - To capture Contact's First Name
  • Text - To capture Contact's Last Name
  • Email - To capture Contact's Email
  • Checkbox - To capture whether Contact is read to share his/her date of birth
  • Date - To capture Contact's Date of Birth

I will also set the component visibility of Data element in this way so that it is only visible when the checkbox is checked.

Step 4 - Loop Element To Go Through Each Repeater Information

In this step, I will be adding the loop element to go through each repeater element to process the information collected inside that repeater. 

Step 5 - Assign Information to Single Contact Record

Here, first, I will be creating a record variable of type Contact (Single record) and give it a name as "SingleContact". Then I will be using the Flow assign element to assign FirstName, LastName and Email to SingleContact's FirstName, LastName and Email respectively.

One important thing in this assignment where I will be assigning the SingleContact's AccountId with the selected Account's ID from the DataTable.

Step 6 - Check Whether Date Of Birth Is Shared

Now, I will be checking whether the repeater block's checkbox (which represents whether the contact is ready to share his/her date of birth) is checked or not?

Step 7 - Assign Date Of Birth

If the checkbox is checked (which is tested in Step 6), I will be adding a new assignment element in the flow where I will be assigning SingleContact's Date of Birth with Repeater Element's Date Of Birth.

Step 8 - Add SingleContact To List Of Contacts

For this step, I will be creating a new record variable of type Contact, but this time I will select multiple records. My intention is to store all contacts inside this list variable. I will give the name of the variable as allContacts.

I will adding the assignment element to store singleContact inside allContacts. And that's the end of loop.

Step 9 - Insert All Contacts

Finally, at the end of the loop, I will be using the Create Records elements to save all the contacts using the allContacts list variable.

Final Flow

Conclusion

I hope this blog post and the video will help you to understand this new powerful feature. As we embark on the journey through Salesforce Summer '24, the introduction of the Flow Repeater Component marks a significant milestone in the evolution of Salesforce Flow. By simplifying the process of collecting user input and constructing lists of records, this innovative feature empowers organizations to streamline workflows, drive productivity, and deliver exceptional user experiences.

Stay tuned for more insights and updates as I explore the endless possibilities of Salesforce Summer '24. Unlock the full potential of your Salesforce org with the Flow Repeater Component, and elevate your business to new heights of success!

Happy Trailblazing!

Disclaimer

This article is not endorsed by Salesforce, Google, or any other company in any way. I shared my knowledge on this topic in this blog post. Please always refer to Official Documentation for the latest information.

Comments

My Favourite 5 Essential Kubernetes GitHub Projects

My Favourite 5 Essential Kubernetes GitHub Projects

Sudipta Deb

Sudipta Deb

Founder of Technical Potpourri, Co-Founder of Shrey Tech, Enterprise Cloud Architect

Welcome to the world of Kubernetes, where the orchestration of containers meets scalability, resilience, and efficiency. In today's tech landscape, where agility and scalability are paramount, Kubernetes emerges as a cornerstone technology, revolutionizing the way we deploy, manage, and scale containerized applications.

Quick Introduction

At its core, Kubernetes is an open-source platform designed to automate the deployment, scaling, and management of containerized applications. Originally developed by Google and now maintained by the Cloud Native Computing Foundation (CNCF), Kubernetes provides a robust infrastructure for orchestrating containers at scale, regardless of the underlying infrastructure.

Imagine you have a fleet of containers, each containing a specific component of your application. Now, picture Kubernetes as the conductor of an orchestra, seamlessly coordinating these containers, ensuring they run efficiently, and dynamically adjusting their placement and resources based on demand.

The form you have selected does not exist.

Here's are my 5 favourite open-source GitHub projects to help you in your Kubernetes journey:

Minikube

Minikube is a tool that enables you to run Kubernetes clusters locally on your machine. It's designed to make it easy for developers to experiment with Kubernetes or to develop applications that will eventually be deployed on Kubernetes clusters. Minikube is a valuable tool for developers looking to gain hands-on experience with Kubernetes or for teams wanting to streamline the development and testing of Kubernetes-based applications in a local environment. It provides a lightweight and convenient way to run Kubernetes clusters locally, helping to accelerate the development and deployment of containerized applications.

Link: https://github.com/kubernetes/minikube

kube-state-metrics

kube-state-metrics (KSM) is a simple service that listens to the Kubernetes API server and generates metrics about the state of the objects. (See examples in the Metrics section below.) It is not focused on the health of the individual Kubernetes components, but rather on the health of the various objects inside, such as deployments, nodes and pods.

kube-state-metrics is about generating metrics from Kubernetes API objects without modification. This ensures that features provided by kube-state-metrics have the same grade of stability as the Kubernetes API objects themselves. In turn, this means that kube-state-metrics in certain situations may not show the exact same values as kubectl, as kubectl applies certain heuristics to display comprehensible messages. kube-state-metrics exposes raw data unmodified from the Kubernetes API, this way users have all the data they require and perform heuristics as they see fit.

Link: https://github.com/kubernetes/kube-state-metrics

Kubernetes Dashboard

Kubernetes Dashboard is a general purpose, web-based UI for Kubernetes clusters. It allows users to manage applications running in the cluster and troubleshoot them, as well as manage the cluster itself.

As of version 7.0.0, we have dropped support for Manifest-based installation. Only Helm-based installation is supported now. Due to multi-container setup and hard dependency on Kong gateway API proxy it would not be feasible to easily support Manifest-based installation.

Additionally, we have changed the versioning scheme and dropped appVersion from Helm chart. It is because, with a multi-container setup, every module is now versioned separately. Helm chart version can be considered an app version now.

Link: https://github.com/kubernetes/dashboard

Kubespray

Kubespray is an open-source project designed to facilitate the deployment, scaling, and management of Kubernetes clusters. It is built on top of Ansible, a popular configuration management and automation tool, and provides a set of Ansible playbooks to automate the installation and configuration of Kubernetes across multiple nodes.

Link: https://github.com/kubernetes-sigs/kubespray

Popeye

Popeye is an open-source tool designed to analyze Kubernetes cluster configurations and provide insights into potential issues, security vulnerabilities, and best practices. It performs static analysis on Kubernetes YAML files or live clusters and generates reports highlighting areas where the cluster configuration may deviate from recommended practices or expose security risks.

Link: https://github.com/derailed/popeye

Conclusion

I hope this list of open source project will help you in your Kubernetes journey. I will be sharing more contents around Kubernetes in near future in my blog and also in my youtube channel - technical potpourri. So let's be connected. 

Disclaimer

This article is not endorsed by Salesforce, Google, or any other company in any way. I shared my knowledge on this topic in this blog post. Please always refer to Official Documentation for the latest information.

Comments

Deploying Profile & Permission Set Changes Through Copado

Deploying Profile & Permission Set Changes Through Copado

Sudipta Deb

Sudipta Deb

Founder of Technical Potpourri, Co-Founder of Shrey Tech, Enterprise Cloud Architect

Welcome to my technical blog series on optimizing Salesforce deployments using Copado! In this introductory post, I will delve into the significance of efficient deployment strategies within Salesforce environments and how Copado emerges as a game-changer in this realm.

Salesforce, being a versatile CRM platform, often undergoes frequent updates, customizations, and configurations to align with evolving business requirements. However, implementing these changes seamlessly across different environments (such as sandbox, staging, and production) while ensuring data integrity and minimizing disruptions is a formidable challenge.

Enter deployment strategies. A robust deployment process is pivotal for maintaining the integrity and functionality of a Salesforce instance, enabling organizations to push changes efficiently while mitigating risks associated with human errors and system inconsistencies.

Copado is a comprehensive Salesforce release management platform designed to streamline and automate the deployment lifecycle. Leveraging Copado, organizations can orchestrate seamless deployments, from development through to production, with enhanced visibility, control, and efficiency.

The form you have selected does not exist.

In this document, I will be covering multiple scenarios to explain how to deal with Profile/Permission Set deployments using Copado.

Below are the scenarios covered in this document - 

  • Deploying new object & field level permission through Profile/Permission Set
  • Deploying existing object & field permission change through Profile/Permission Set
  • Deploying New Page Layout Assignment(No Record Type) through Profile/Permission Set
  • Deploying Existing Page Layout Assignment(With New Record Type) through Profile/Permission Set
  • Deploying Existing Page Layout Assignment(With Existing Record Type) through Profile/Permission Set
  • Deploying New FlexiPage Layout Assignment as App Default through Profile/Permission Set

Pipeline

Below is the screenshot of the pipeline configuration I will be using. I will be mainly making changes in DEV1 environment and through Copado, I will be publishing those changes into next environment which is UAT.

Scenario 1 - Deploying New Object & Field Level Permission Through Profile/Permission Set

  • New Object Name - Hello Canada
  • New Field Name - Email
  • New Permission Set Name - Hello Canada
    • Object Level Permission - Available, Visible, Read
    • Field Level Permission - Read & Edit

Commit Configuration -

Since all three (object, field and permission set) are brand new and not available in the target environment, during the commit we need to select all of them. Do not select the “Retrieve Only” checkbox.

Here is the screenshot - 

Scenario 2 - Deploying Existing Object & Field Level Permission Through Profile/Permission Set

  • Existing Object Name - Hello Canada
  • Existing Field Name - Email
  • Existing Permission Set Name - Hello Canada
    • Object Level Permission - Available, Visible, Read, Create
    • Field Level Permission - Read 

Commit Configuration -

Since all three (object, field and permission set) are existing and available in the target environment, during the commit we need to select all of them. But since there are no changes in the object and field (all changes are literally in the permission set), mark “Retrieve Only” checkbox checked for object and field.

Here is the screenshot -

Scenario 3 - Deploying New Page Layout Assignment (No Record Type) Through Profile/Permission Set

  • New Page Layout Name - New Hello Canada
  • Existing Profile Name - Admin

Commit Configuration -

Since the page layout is new (not available in the destination org), but the profile is an existing profile, during the commit we need to select both of them. But make sure “Retrieve Only” checkbox is unchecked for both.

Here is the screenshot -

Scenario 4 - Deploying Existing Page Layout Assignment (With New Record Type) Through Profile/Permission Set

  • Existing Page Layout Name - New Hello Canada
  • Existing Profile Name - Admin
  • New Record Type - New Hello Canada Record Type

Commit Configuration -

Since the page layout and the profile are the existing ones, but the record type is new (not available in the destination org), during the commit we need to select all three. But make sure “Retrieve Only” checkbox is checked only for layout (assuming there is no layout changes and all we are deploying page layout assignment only).

Here is the screenshot -

Scenario 5 - Deploying Existing Page Layout Assignment (With Existing Record Type) Through Profile/Permission Set

  • Existing Page Layout Name - New Hello Canada
  • Existing Profile Name - Admin
  • Existing Record Type - New Hello Canada Record Type

Commit Configuration -

Since the page layout, record  type and the profile - all are the existing ones, during the commit we need to select all three. But make sure “Retrieve Only” checkbox is checked for layout (assuming there is no layout changes and all we are deploying page layout assignment only) and record type.

Here is the screenshot -

Scenario 6 - Deploying New FlexiPage Layout Assignment as App Default Through Profile/Permission Set

  • New FlexiPage Layout Name - Hello Canada
  • Existing App Name - Hello World

Commit Configuration -

Add the page layout and app in the metadata. And please do not mark “Retrieve Only” checkbox checked.

Conclusion

In this introductory post, I have laid the foundation for our exploration of Copado's capabilities in optimizing Salesforce deployments. Over the coming weeks, I will delve deeper into specific deployment scenarios, best practices, and advanced features to empower organizations to unleash the full potential of their Salesforce investment.

Stay tuned for my next post, until then, feel free to explore Copado's website and start your journey towards seamless Salesforce release management.

Disclaimer

This article is not endorsed by Salesforce, Google, or any other company in any way. I shared my knowledge on this topic in this blog post. Please always refer to Official Documentation for the latest information.

Comments

Google Cloud Next ’24 Day 3 Recap

Google Cloud Next ’24 Day 3 Recap

Sudipta Deb

Sudipta Deb

Founder of Technical Potpourri, Co-Founder of Shrey Tech, Enterprise Cloud Architect

Last week in Las Vegas, more than 30,000 people attended Google Cloud Next 2024, together with 2,500 partners. The company's redoubled commitment to generative AI optimization and AI in general was evident in Google Cloud Next 2024.

The key points from the company's premier cloud event are outlined here.

  • This week's Google Cloud Next 2024 was concluded on Thursday by Google Cloud.
  • With 2,500 partners and over 30,000 guests, Google Cloud Next 2024 had a 100% rise.
  • Google reaffirmed its commitment to generative AI and AI in general with Google Cloud Next 2024.

This year, Google Cloud Next was held in Las Vegas instead of its customary venue in San Francisco, as the annual cloud conference. Google Cloud Next 2024 witnessed the company's increased commitment to generative AI and artificial intelligence (AI) in general, in addition to a new location.

The form you have selected does not exist.

“One of the reasons Cloud is showing so much progress is our deep investments in AI. We’ve known for a while that AI will be the next technology to transform companies. Our investments in AI infrastructure and models help put us at the forefront of the AI platform shift. And we’re proud that today more than 60% of funded generative AI startups, and nearly 90% of gen AI unicorns are Google Cloud customers,” noted Sundar Pichai, CEO of Google.

Ram Boreda, VP of Products at Egnyte, attended Google Cloud Next 2024 in Las Vegas and attests to Google Cloud’s success with startups. “The startup ecosystem leveraging GCP has grown tremendously,” he told Spiceworks News & Insights. “The demo grounds had more vendors and serious products. This shows that GCP has established itself as a leader in the new wave with AI.”

“Every product in Google’s catalog had an AI uplift,” Boreda noted. “Announcements were made for every product portfolio – modern Infra Cloud, Developer Cloud, Data Cloud, Security Cloud, Collaboration Cloud.”

AI Infrastructure

Axion central processing units, Google's answer to AWS's Graviton, Alibaba's Yitian 710 server, Microsoft's Azure Maia 100 and Cobalt 100 chips, and Alibaba are currently part of Google's infrastructure optimization efforts for AI.

While we know that Axiom uses Arm's Neoverse 2, benchmarking information, architectural specifics, and other technical documentation regarding Google's proprietary Arm-based silicon for cloud infrastructure are still unknown.

Google claims that Axiom processors, which are intended for general-purpose computing, deliver 60% greater performance and are 60% more energy efficient than comparable X86 chips. Additionally, the company claimed that Axiom outperforms Arm-based processors made by Microsoft and AWS by 30%.

Boreda stated, "Google is catching up to AWS and Microsoft, who have chips that are already built on the Arm architecture. All of this results in a growing trend in costs.

The most potent tensor processing unit from Google, the TPU v5p, which can grow to tens of thousands of chips, was also made generally available. 8,960 chips make up a single v5p pod, which is nearly twice as many as a TPU v4. In addition, TPY v5p offers four times greater scalability, three times more high-bandwidth memory, and twice as many floating point operations per second.

With Google TPUs, NVIDIA GPUs (H100), NVIDIA GB200 support from 2025, AI-optimized storage (Hyperdisk ML), dynamic workload management [Dynamic Workload Scheduler], and Google Axion ARM processor for datacenter, among other things, Boreda stated, "AI Infrastructure gets a big boost."

Vertex AI Updates

First up, clients may create and use AI agents with the Vertex AI Agent Builder, a no-code service. It integrates Google Search, developer tools, and several major language models.

The business has decreased hallucinations and grounded results (i.e., displayed results sourced from reputable sources) by implementing vector search and retrieval augmented generation (RAG). Gemini's extensive language models are utilized by Vertex AI Agent Builder. Google demonstrated a number of use cases, such as contract management and retail.

More AI models are also available in Vertex AI today, such as the new Claude 3 family of AI models from Anthropic, Gemini 1.5 Pro, CodeGemma (Google's coding aid model), Imagen 2.0 (text-to-image technology), and others.

Notably, the public preview of Gemini 1.5 Pro is now available. Its multimodal context window increases to about a million tokens.

Workspace AI Updates

More AI features are being added to Google Workspace, the productivity package that billions of people use on a daily basis. Among them are a few of them:

Gmail voice suggestions to write emails, improving drafts
Spreadsheet templates and change alerts
Improved Docs organization features
More significantly, Google Vids, a new AI-powered video creation service, is coming to Workspace. Vids is designed to work inside Docs and Sheets for a collaborative experience to meet organizational objectives, including producing explainer films, product decks, etc. It is currently available for restricted testing.

Google plans to counter Microsoft's Copilot initiative by integrating Gemini into all of its app stack products. 

Hyperdisk Storage Pools

Google's Hyperdisk Storage Pool, a block storage service designed to achieve cost and computation efficiency, is one of the less publicized improvements. It makes it possible for developers to employ storage pooling for various workloads, including AI inferencing.

According to Google, "Hyperdisk ML offers cost efficiency through read-only, multi-attach, and thin provisioning and accelerates model load times up to 12X compared to common alternatives." "It offers up to 1.2 TiB/s of aggregate throughput per volume and allows up to 2,500 instances to access the same volume—over 100X greater performance than Microsoft Azure Ultra SSD and Amazon EBS io2 BlockExpress."

Hyperdisk Storage Pools let users make efficient use of their resources while lowering their overall cost of ownership and management.

Conclusion

As we bid farewell to Google Cloud Next 2024, a sense of awe and inspiration lingers in the air. The last day of this groundbreaking event has come to a close, leaving us with a treasure trove of new announcements and insights to digest and explore.

From the unveiling of cutting-edge technologies to the deep dives into the future of cloud computing, each day of Google Cloud Next has been a testament to the boundless innovation and ingenuity that define the tech industry. As we reflect on the wealth of knowledge gained and the connections made, it's clear that the impact of this event will reverberate far beyond the walls of the Mandalay Bay Convention Center.

But our journey doesn't end here. As we move forward, armed with the latest tools and insights from Google Cloud Next, we embark on a new chapter of discovery and growth. The innovations unveiled during this event will continue to shape the way we work, collaborate, and innovate in the years to come.

So, as we say goodbye to Google Cloud Next 2024, let us carry forward the spirit of curiosity, creativity, and collaboration that has defined these unforgettable days. And remember, the future of technology is bright, and with each new discovery, we inch closer to realizing its full potential.

Until we meet again, may your dreams be bold, your aspirations lofty, and your journey through the world of technology filled with endless possibilities. Farewell, Google Cloud Next 2024 - until next time!

Disclaimer

This article is not endorsed by Salesforce, Google, or any other company in any way. I shared my knowledge on this topic in this blog post. Please always refer to Official Documentation for the latest information.

Comments

Google Cloud Next ’24 Day 2 Recap

Google Cloud Next ’24 Day 2 Recap

Sudipta Deb

Sudipta Deb

Founder of Technical Potpourri, Co-Founder of Shrey Tech, Enterprise Cloud Architect

Welcome back, tech aficionados! Day two of Google Cloud Next 2024 is done, and the excitement was palpable as developers from around the globe gather at the illustrious Mandalay Bay Convention Center in Las Vegas. My focus shifts to the Developer Keynote, where Google unveiled a treasure trove of new announcements set to revolutionize the world of software development.

From innovative tools and platforms to groundbreaking updates on existing technologies, the Developer Keynote promised to be a showcase of ingenuity and creativity.

Join me as I unpack the highlights of the Developer Keynote, diving deep into the latest offerings from Google that are poised to shape the future of software development. From AI-driven enhancements to developer-friendly features, there's something for everyone in today's announcements.

So, grab your laptops and get ready to embark on a journey into the heart of developer innovation. Together, let's explore the cutting-edge advancements that are propelling us towards a future limited only by our imagination. Welcome to day two of Google Cloud Next 2024 - where the code meets the cloud, and innovation knows no bounds!

The form you have selected does not exist.

Developer Keynote

The Developer Summit Keynote on Day 2 further fueled the momentum behind Google Cloud Next 2024.

The developers and architects of Google Cloud solutions were the target demographic that the Developer Keynote specifically targeted. And the meeting did not let me down!

Here's a recap in case you missed it.

Build: Generative AI Across The Developer Workflow

The standout feature is Gemini Code Assist, which allows AI-powered code completions and now supports a context window with one million tokens. Through the analysis of a developer's unique cloud resources, such as logs and configurations, Gemini Cloud Assist applies this AI support to cloud operations.
Google is integrating generative AI into BigQuery and other tools to analyze data with natural language and multimedia inputs. Vector search and unstructured data embedding are being added to its databases. In a demonstration, an AI app that generated floor plans, suggestions, and ideas for house design in response to multimedia cues was built in a matter of minutes.
In order to increase developer productivity, Google wants to integrate contextualized, configurable generative AI into data analytics, ops, coding, and application development.

New things that makes this possible:

  • App Hub - Regardless of the particular Google Cloud products that are used, App Hub—which was unveiled on Day 2—offers a precise, current depiction of deployed applications and their resource dependencies thanks to its strong connection with Google Cloud Assist.
  • BigQuery continuous queries - BigQuery can now process SQL continuously over data streams in preview, allowing for real-time pipelines with AI operators or reverse ETL.
  • Natural Language support in AllowDB - Support for Google's cutting-edge ScaNN algorithm gives AlloyDB customers access to improved vector performance, which underpins a number of Google's most well-known services.
  • Gemini Code Assist in Apigee API Management - Utilize Gemini's natural language prompts to assist you in developing enterprise-grade APIs and integrations.

Run: Deploying And Scaling Generative AI

With GKE for reliable Kubernetes-based AI programs and Cloud Run for quick serverless deployments, Google Cloud makes it possible to launch and scale generative AI applications. The latest additions include Quick Start options, GKE connections for running big language models like Gemma, and Cloud Run Application Canvas for quickly creating AI apps.

New things that make this possible:

  • Cloud Run application canvas - Create, edit, and implement AI apps in Cloud Run. Vertex AI integrations allow you to quickly and easily use generative APIs from Cloud Run services.
  • Gen AI Quick Start Solutions for GKE - Utilize AI on GKE by integrating it with Ray or using a Retrieval Augmented Generation (RAG) method.
  • Support for Gemma on GKE - Gemma is Google's open model built on Gemini, and GKE provides multiple ways to operate it. Even better, the performance is superb.

Operate: Handling AI Behaviors

Emergent behaviors from AI apps can lead to new problems, Google Cloud Reliability Advocate Steve McGhee stated. "Dynamic and chaotic" is how Charity Majors described contemporary systems in contrast to dependable heritage systems.

But generative AI also offers fresh resources for comprehending and handling change:

  • Prompt Management and Rapid Evaluation are two Vertex AI MLOps that are useful for experimenting with prompts and evaluating the performance of models.
  • To identify unregulated APIs that can pose security problems, use shadow API detection.
  • Confidential Accelerators provide AI/ML workloads with hardware data protection.
  • To maximize GPU utilization and speed up cold starts, preload models and GKE containers.

New things that make this possible:

  • Vertex AI MLOps Capabilities - While Vertex AI Rapid Evaluation assists users in assessing model performance when iterating on the optimal prompt design, Vertex AI Prompt Management allows customers to experiment with migration and tracking of prompts and parameters in preview, allowing them to compare prompt iterations and assess how small changes impact outputs.
  • Shadow API Detection - Shadow API identification in Advanced API Security preview assists you in identifying APIs that lack adequate governance or supervision and may be the cause of harmful security incidents.
  • Confidential Accelerators for AI workloads - The A3 machine series' confidential virtual machines, which use NVIDIA Tensor Core H100 GPUs to manage sensitive AI and machine learning data, expand hardware-based data and model protection from the CPU to the GPU.
  • GKE container and model preloading - GKE can now accelerate workload cold-start in preview to maintain low AI inference latency, increase GPU usage, and save costs.

Conclusion

As I wrap up my coverage of day two at Google Cloud Next 2024, the air is buzzing with excitement and anticipation for what's to come. The Developer Keynote has left me inspired and eager to dive deeper into the world of software development, armed with the latest tools and technologies unveiled by Google.

I promise to continue bringing you comprehensive recaps of each day's events, including all the groundbreaking announcements and insights that emerge. So stay tuned, as I am preparig the recap of day three of Google Cloud Next.

In the meantime, let's reflect on the wealth of knowledge and inspiration gained from Day 2's Developer Keynote. From AI-driven enhancements to developer-friendly features, the possibilities seem endless, and the future looks brighter than ever.

So, until next time, fellow developers and tech enthusiasts, let's continue to embrace the spirit of innovation and collaboration as we journey towards a future limited only by our imagination. Stay tuned for more exciting updates from Google Cloud Next 2024!

Disclaimer

This article is not endorsed by Salesforce, Google, or any other company in any way. I shared my knowledge on this topic in this blog post. Please always refer to Official Documentation for the latest information.

Comments