The app for independent voices

Bad Microservices:

• Inconsistent naming convention for APIs.

• No health checks to find service availability.

• Manual scaling of microservices based on traffic.

• Single database shared across many microservices.

• Inconsistent database and table definitions across microservices.

Good Microservices:

• Standardized naming convention of APIs using code generation.

• Standardized health check API URLs using code generation.

• Infrastructure as code and automation for scaling microservices.

• Separate database for each microservice for loose coupling.

• Standardized database and table definitions using code generation.

What else would you add?

Feb 4
at
9:22 AM

Log in or sign up

Join the most interesting and insightful discussions.