What problem does it solve? The problem is that managing synergy between client and server is typically done in two separate repositories: frontend and backend. This can make maintenance between the two cumbersome and error-prone, especially for large projects.
The solution: With Orcha, you house your frontend and backend in a monorepository and have a shared folder that acts as a single source of truth for your project’s domain. This allows for robust, type-safe communication between client and server. Not only that but with Orcha queries, you can ask your server for the exact data schema you want including relational joins between entities (powerful feature). Orcha relies heavily on Typescript generics to do all the heavy lifting to ensure your project is type-safe throughout the entirety of your project’s development.
Who gets the most benefit from this framework: I see full-stack developers getting the most benefit from it and companies wanting a novel and intuitive way to build large-scale web applications needing user authentication (e.g. multiple user types) and real-world domain modeling.
My promise: The promise I have is unprecedented developer experience. As a developer, I can promise that you will find working with the framework intuitive and watch your productivity skyrocket.
To read more on this blog visit: Introducing OrchaJS: A TypeScript-Native Client-Server Facilitator
Author: Jeremy Zacharia