Microservice Contracts

[ynigoreyes]

We need to create a template for how we are going to document the contracts for our micros so that we can all get on the same page.

We need:

• Versioning
• Naming Conventions
• a tool that will help us monitor interaction between micros. If we encounter a bug, how will we know whos input we received.
• (More to come, can't think of any right now)

[NilsG-S]

By contracts do you mean APIs?

[ynigoreyes]

I mean contract... Like how the micro appears to users/other services. It was the terminology used in a lot of micro architecture guides so I thought I'd use it.

[NilsG-S]

From my research, contract is usually conflated with API. Do you mean something like this: https://github.com/TTUSDC/CPCEEDWebAppBackend/wiki/API-Reference?

[ynigoreyes]

Yeah pretty much. I didn't know that one was already made

[NilsG-S]

It needs to be updated, but we have the basic idea