OpenAPI or gRPC is a better path forward

Posted Aug 23, 2025 15:26 UTC (Sat) by lyda (subscriber, #7429)
Parent article: The "impossibly small" Microdot web framework

Defining an API in OpenAPI or gRPC is better way forward because it allows developers to generate more of the application, keep clients, server and testing in sync reduces a slew of errors and reduces maintenance burdens.

When I wrote a lot of python, frameworks like this seemed great. But there's a better way. If you define the OpenAPI definition first, you can then generate the server, you can generate all the clients, you can generate tests for the server and client, as well as fuzz tests for the server. Less common, but you can do the same with gRPC. It also allows you to more easily move from one technology to another.

OpenAPI or gRPC is a better path forward

Posted Aug 24, 2025 3:10 UTC (Sun) by ssmith32 (subscriber, #72404) [Link] (1 responses)

Better way forward for what?

Certainly not for the problem domain covered in the article.

OpenAPI or gRPC is a better path forward

Posted Nov 3, 2025 1:38 UTC (Mon) by Rudd-O (guest, #61155) [Link]

Actually it's perfect for that problem domain, and that S exactly how ESPHome solves that exact problem — gRPC on device (ESP / RP2040) when communicating with clients like Home Assistant. Works beautifully, is fast, and supports encryption too.