Question 1

How do I add a new API endpoint in Microservice?

Accepted Answer

You need to define the route in the gateways layer (e.g., gatein.go), implement the corresponding use case and entity, following the example in the public/v1/bar route. The README outlines the clean architecture layers for guidance.

Question 2

Does Microservice support gRPC?

Accepted Answer

Not currently; gRPC support is listed in the ToDo section and not yet implemented. You would need to add it manually if required, which might involve significant integration work.

Question 3

Microservice vs Go kit: which one should I use?

Accepted Answer

Microservice provides a more opinionated clean architecture with built-in endpoints like health checks and Swagger, while Go kit is a toolkit offering more flexibility but less out-of-the-box functionality. Choose based on whether you value structure or customization.

Question 4

How to configure environment variables in Microservice?

Accepted Answer

Set environment variables like GATE_IN_TITLE, and the framework uses dsbasko/go-cfg to manage configuration from both YAML files and env vars, as shown in the README with the example export command.

Question 5

Is Microservice ready for Kubernetes deployment?

Accepted Answer

Yes, it has built-in health checks (/healthz, /readyness) and metrics (/metrics) suitable for Kubernetes, but Docker support is pending, so you might need to create your own Dockerfile for containerization.

Question 6

How to extend validation rules in Microservice?

Accepted Answer

Since it uses go-playground/validator, you can define custom validation tags in your structs as per the validator library's documentation, leveraging its integrated validation features.

Microservice

What is Microservice?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions