¿Qué es API en cloud-native?

An API (application programming interface) is the interface cloud-native services within a microservices architecture connect with. APIs have rules and specifications for interacting software components and data exchange, acting as contracts, which for HTTP APIs can be written in the OpenAPI Specification (OAS) which is a standard description format. Through loose coupling, APIs are used to create and scale services in a reusable and interoperable space. They are also useful when deploying.

Both Cloud-native and SaaS use cloud computing, but their approach with software development and delivery are not the same. 

For example:

• Cloud-Native Apps: Built especially for a cloud. They use containers, microservices and orchestration with agility and scalability. Companies are more likely to use cloud-native apps if they need more control over underlying infrastructures and to customize. DevOps is necessary for deploying and managing cloud-native apps.
• : Las aplicaciones están alojadas/administradas por un proveedor, lo que significa que tienen una personalización limitada; por otro lado, los clientes pueden acceder a las aplicaciones SaaS en línea. Las empresas pagan mediante suscripciones y utilizan SaaS para la implementación/el mantenimiento.: Applications are hosted and managed by a provider, so there is less flexibility with customization; but on the plus side, SaaS apps are accessible to customers online. Businesses pay via subscriptions and rely on the provider for deployment and maintenance.

Algunas de las cosas en las que tendrá que pensar al diseñar/administrar API en entornos nativos de la nube son:

• Multi-API Complexity: When using multiple APIs, it’s important to look at possible issues related to design and documentation. Also consider any potential problems with documentation.
• Versioning: You need to carefully version APIs when they evolve to avoid issues with backward compatibility.
• Seguridad: Implement appropriate security measures to decrease the chance of risks associated with API usage, as they can expose sensitive data or functionalities.
• Rendimiento: Make sure you’ve optimized your APIs for high performance/scalability as they normally manage varying workloads.

Adhiérete a estas prácticas:

• Diseño API-First: Utilice el diseño de API antes de la implementación del servicio; esto es crucial para garantizar contratos claros.
• Estandarización: Utilize REST, GraphQL, as well as any other other API design standards; be consistent when doing so. Describe HTTP APIs in the OpenAPI Specification.
• Documentación: Keep your API documentation up-to-date and ensure it’s comprehensive.
• Versioning: Define your versioning strategy before implementing it.
• Seguridad: Use API safeguards, such as encriptación, autenticación y aplicación de autorización.
• API Gateway: Give API consumers one entry point, which centralizes authentication, authorization and request limits (CNCF).
• Monitoreo/Analítica: Monitor your API usage/performance over the long run.

Cloud-native service discovery detects/registers a cloud environment’s services. After it has done this, the other services in the infrastructure should be able to communicate with and discover them; this is done via identifiers or logical names.

El dinamismo es crucial en entornos en la nube. El descubrimiento de servicios también es importante para la comunicación y el acoplamiento flexible.

La capacidad de descubrimiento de servicios funciona dentro de estos dos aspectos de la siguiente manera:

• Dynamic Scaling: new instances can be added and removed when demand goes up or down. Service discovery is important for registering this rollercoaster and making them discoverable.
• Resiliency: Service discovery will notify you of instance failures before removal from the directory, so other services can adjust their routing behavior. This is required for service uptime and availability.