How should be built the ideal cloud-native framework (part 2)

The backend

The database

The admin interface

The API and the API protocols

The authentication

The clients

The cloud-native tools

  • The logs of your services will be sent and centralized into Fluentd
  • Metrics (servers loads, time to answer requests, etc…) will be stored into Prometheus
  • Each stage of every request will contact Jaeger to provide distributed tracing. This allows us to see the whole journey of a request, and instantly see which service went wrong.

The development process

About the license

--

--

--

French developer, backend/ERP software. Opensource advocate and passionate, always learning. http://empower.sh

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Dart inheritance

Day 9, CoreProgramming-1

Amazon Web Services — Basic Architecture

ApeRocket Newsletter #1, November 1st 2021

How to send messages to multiple platforms from your shell scripts

How we made our staging environment useful

How to use the LIKE Operator and Wildcard Characters in SQL

Login fails if the user has a broken arm

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
YannickB

YannickB

French developer, backend/ERP software. Opensource advocate and passionate, always learning. http://empower.sh

More from Medium

gRPC Request Routing (Header Based) AWS ALB

101 AWS Lambda tutorial for Go developers — API Gateway (Part 2)

Redis to REST, securely

GoFrame 101(rk-boot): Manage config files in Cloud Native way