✨Our Features

There are several good-to-have features that an API in the cloud should have:

  1. Scalability: The API should be able to handle an increasing number of requests without compromising on performance.

  2. Security: The API should have secure authentication and authorization mechanisms to ensure that only authorized users have access to the API and its resources.

  3. Reliability: The API should be reliable and available at all times, with minimal downtime or disruptions.

  4. Documentation: The API should be well-documented, with clear instructions on how to use it, including sample code, parameters, and responses.

  5. Monitoring and Analytics: The API should provide comprehensive monitoring and analytics tools that allow developers to track usage, identify performance bottlenecks, and optimize the API.

  6. Versioning: The API should support versioning, allowing developers to make changes and improvements to the API without breaking existing integrations.

  7. Caching: The API should include caching mechanisms to improve performance and reduce the load on the server.

  8. Rate limiting: The API should include rate limiting to prevent abuse and ensure fair usage of the API.

  9. Webhooks: The API should support webhooks, allowing developers to receive real-time notifications of changes and updates.

  10. Integration with other services: The API should be able to integrate with other cloud services, such as databases, messaging services, and storage services, to provide a seamless user experience.

Feature in Depth

Evolution is a cloud-enabled, devops-ready practice for any applications, built to be deployed on kubernetes.

  • Microservices using Clean Architecture

  • Async Communication using Message Queue

  • GRPC Communication

  • Infrastructure as code

  • Service Mesh (Kuma/Istio)

  • Container (Podman/docker)

  • Terraform

Key Features

  • The services use a Clean Architecture approach using CQRS

  • We have used Serrilog for Logging and can be visible in Serrilog Dashboad.

  • The Identity Service has an in build simple Admin Panel to view and edit roles/users.

  • The Service exposes an health check endpoint with system resources info.

  • The Service also expose metrics for Promethues and can be Integrated With Grafana.

  • The service communicates to each other for eventual consitency via MSMQ -> RabbitMQ

  • The service communicate also via GRPC for syncronus calls.

PreviousScope & TechnologiesNextApplication Architecture

Last updated