# Building API server for terraphim - moving from Poem to Axum

**URL:** <https://terraphim.discourse.group/t/building-api-server-for-terraphim-moving-from-poem-to-axum/20>\
**Category:** General\
**Tags:** terraphim\
**Created:** [8 December 2023 14:38 UTC](https://terraphim.discourse.group/t/building-api-server-for-terraphim-moving-from-poem-to-axum/20 "2023-12-08T14:38:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![alex](https://yyz2.discourse-cdn.com/free1/user_avatar/terraphim.discourse.group/alex/32/21_2.png) [@alex](https://terraphim.discourse.group/u/alex)\
**Post date:** [8 December 2023 14:38 UTC](https://terraphim.discourse.group/t/building-api-server-for-terraphim-moving-from-poem-to-axum/20/1 "2023-12-08T14:38:32Z")

</div>

After prototyping API in poem for several years, I had to move to Axum - due to Poem limitations on implementing Type for each data structure.  
See [Poem discussion](https://github.com/poem-web/poem/discussions/219).

I see middleware API as a thin layer on top of Terraphim AI and Poem forces to implement a lot of boilerplate to expose endpoint with OpenAPI.  
More details to come in writing. I also have 8+ hours of pair programming videos, which didn’t result in success.