We have just published an article on Codemotion about "Design-first gRPC APIs for microservices: a sample workflow for parallel teamwork".
Key Takeaways:
- You can allow teams to work in parallel by designing gRPC APIs before starting to code.
- When teams work in parallel, you significantly decrease the time-to-market of your products.
- A sample workflow has a few key stages.
- The teams start by designing the gRPC API
- Then, producer and consumer teams can work in parallel on their microservices.
- The consumer team can use mocks to simulate the backend producer service.
- Communicating feedback about the API specification during the development phase is essential.
- Once the microservices are ready, they can test them together and release them to production.
- You can start by onboarding just one API to this new workflow; you don’t have to migrate your whole company, to begin with
- Working in parallel is excellent for team morale as there is less hard-deadline pressure
- You can estimate the return on investment by using a simple spreadsheet.
