El enlace al zip de la clase.
https://github.com/apigee/apijam/blob/master/Module-1/Resources/Hipster-Products-API_With_CORS_Config.zip
Retail Store en Google Cloud Platform
Lo que aprender谩s sobre GCP para ecommerce
Etapas clave y MLOps
Arquitectura de alto nivel
Tour de la aplicaci贸n de retail
Backend as a Service y modelo de seguridad
Introducci贸n al proyecto
Medici贸n de interacciones
Setup de Google Tag Manager
Etiquetando con Google Tag Manager
Etiquetas relevantes para CLV
Integraci贸n con servicios
Exposici贸n de servicios con Apigee
Servicios expuestos con APIs
驴Qu茅 son las APIs?
Apigee
Creaci贸n de tu primer API Proxy en Apigee
Administraci贸n de APIs con Apigee
Creando un portal de desarrolladores
Interactuando con el portal de desarrolladores
Insights to Actions
Generaci贸n de modelos AI/ML
Machine Learning con datos estructurados
BigQuery para modelos de Forecasting y LTV
Bigquery ML - Manos a la Obra
Auto ML vs. Bigquery ML
Consideraciones para entrenar un modelo en BigQueryML
Entrenamiento del modelo en BigQuery ML
C贸mo exportar modelos hechos en BQML
Exportando un modelo hecho con BQML
Consumo de servicios de AI/ML
C贸mputo Serverless y Contenedores
驴Qu茅 es Kubernetes?
Consumo de modelos ML mediante BigQuery API
Almacenamiento de predicciones
Ejecuci贸n de predicciones y persistencia
Despliegue continuo con Cloud Run
Ejecuci贸n de despliegue con Cloud Run
Escalamiento de servicios en Cloud Run
AuthN y AuthZ con Cloud Run
Google Marketing Platform
An谩lisis de las predicciones
Segmentamos nuestras Predicciones
Caso pr谩ctico para definir tu estrategia de activaci贸n
Generemos nuestros modelos en la plataforma
Segmentamos nuestras audiencias en BigQuery
Carga tus audiencias y conecta tu medio de activaci贸n
You don't have access to this class
Keep learning! Join and start boosting your career
A developer portal is a key tool for those who want to consume your APIs. In the given context, we are talking about a Developer Portal
, which is designed to provide application developers with a self-service integration experience. This means that they can easily browse your API catalog, review your documentation, and even sign up to start integrating them into their projects.
A Proxy API acts as an interface between the client consuming APIs and the actual service provided. In this context, an upgrade of the Platzi Products API
is being performed through APIG. Here are some important steps to follow:
CORS
(Cross-Origin Resource Sharing) definition is selected.base path
in the code to ensure that the API works correctly.API specifications will allow you to define how your API looks and operates. In the scenario described, the following changes were made:
base path
must match what is defined in the specification.Security Definitions
is added to manage access.HTTP
to HTTPS
for better security.It is important to make these changes carefully and check the syntax to avoid errors.
Once you have your APIs ready, the next step is to create an environment where developers can interact with them: the portal.
Publish
section, a new portal is created.look and feel
of the portal, so that users feel more connected.Platzi Product
API is added to the portal catalog.This process not only allows developers to access your APIs, but also improves the perception and usability of your ecosystem by offering a robust and user-friendly experience.
With these steps, you not only optimize access to your APIs, but also strengthen the relationship with developers by offering integrated and accessible support. Get excited to keep exploring and creating new solutions with APIs!
Contributions 1
Questions 0
El enlace al zip de la clase.
https://github.com/apigee/apijam/blob/master/Module-1/Resources/Hipster-Products-API_With_CORS_Config.zip
Want to see more contributions, questions and answers from the community?