[🚀 FEM-Design API gRPC]

API Refactoring and Cross-Language Strategy

As outlined in issue #962 , the current API requires a substantial refactoring effort. Technical debt has been steadily accumulating, and without intervention, maintainability and scalability will soon become a significant risk.

Contrary to what was initially specified in the original case, we plan to ship a cross-language API tool. This decision is driven by multiple requests for a Python API, in addition to existing C# usage. Supporting multiple languages is therefore a strategic requirement rather than a nice-to-have.

To achieve this, we will adopt gRPC as the core API technology. gRPC enables the creation of a high-performance, scalable, and maintainable API, while naturally supporting cross-language clients. This approach positions our API to become best-in-class in terms of performance, long-term sustainability, and developer experience.

Informations related to the topic are visible in https://github.com/ms-structural/femdesign-api-2.0

Start by reading issue #962 and the related information in the femdesign-api-2.0 repository. The issue names no files, tests, or entry points, so first clarify the gRPC API scope, supported client languages, and concrete definition of done before implementation can begin.