[Terretta]

This is fantastic.

At the same time, there's an ecosystem beyond just the web framework, where rapid iteration is helping a developer write once but leverage multiple tools.

For instance:

  - FastAPI
  - Starlette
  - pydantic
  - sqlmodel
  - postgres

Here's an example discussion for building the full stack yourself: https://medium.com/@lawsontaylor/the-ultimate-fastapi-projec...

The value comes from the sort of community-agreed data model:

Why: https://docs.pydantic.dev/latest/why/

Datamodel code gen: https://docs.pydantic.dev/latest/integrations/datamodel_code...

With this at the core, then API contract, doc, DB, test, and SDK generation are at hand, not to mention easier integration with all of these other projects. And now with

Observability: https://pydantic.dev/logfire

I find no hits on the terms `pydantic` or `openapi` in your docs. Given your choice to include Python as one of the three supported languages, do you have a plan to tie into Pydantic or implement a bridge?

[victorteo]

Hi @Terretta, I plan to generate OpenAPI output for HTTP clients like Postman to import and read. We have things like FastAPI, Starlet, pedantic, sqlmodel and Postgres in Teo. The only thing we lack of is the debugger web interface which we could use Postman after exporting OpenAPI output is implemented.

The logfire is pretty cool and in the future, it will be implemented in Teo's way.

[Terretta]

Thanks for the reply.

To be more clear, it's great you have a similar option for each of these, but having things similar to them isn't the same as having the actually same model that everything else in the ecosystem understands and plays well with.

Or, are you saying, under the hood, you're using literally the same? The docs make it sound as though you're reinventing all these wheels (pardon the Python pun).

[victorteo]

They are similar things. The wheels are reimplemented to suit Teo's architecture.