Why OpenAPI?

[jcorry]

I'm curious what motivated openAPI and it's code generator?

It seems like all of the functionality provided there could be delivered by:

• https://github.com/grpc-ecosystem/grpc-gateway
• https://github.com/grpc-swagger/grpc-swagger

I am a fan of grpc-web for consuming gRPC services with a Vue client, but realize a REST analog is often useful too.

It seems like it would be simpler and with less overhead to use tools from within the same gRPC ecosystem.

I am really enjoying the book! Thank you so much for publishing all of this!

[m110]

Hey @jcorry!

The reason is simply we didn't use gRPC this way yet. The gRPC gateway seems to totally make sense for the kind of communication we've created. On the other hand, REST is very popular for frontend/backend communication, and we wanted to base Wild Workouts on technologies everyone is familiar with.

We might introduce it in the future to simplify the API, but first we'll be focusing on more strategic patterns. Thanks a lot for bringing it up and I'm glad you liked the book! :)

[m110]

Actually, adding gRPC gateway would be a great example of how Clean Architecture enables such changes. In Wild Workouts, it would be just extending the ports layer. :)