The design of FOLIO architecture (microservices and REST) enables any module to be written in a programming language that the developer is comfortable with. So various programming languages and build environments can be utilized.
The back-end modules can utilize any language. The RAML Module Builder (RMB) framework, is a special module that abstracts much functionality and enables the developer to focus on implementing business functions. Define the APIs and objects in RAML files and schema files, then the RMB generates code and provides tools to help implement the module. Note that at this stage of the FOLIO project, only this Java-based framework is available. Other frameworks would be possible.
- Be able to handle the REST interactions according to the API and implement the lifecycle endpoints.
- As explained in the Okapi Guide, Okapi uses HTTP 1.1 with chunked encoding to make the connections to the modules.
- Be able to handle the REST interactions according to the API.
- Be able to manage state and send special headers such as X-Okapi-Tenant.
So far we have concentrated on server-side modules in Java using Vert.x, and client-side in Node.js and React. Because we use them internally, those technologies will have a prominent place in the FOLIO ecosystem and, initially, it may be easiest to get started using them. We provide libraries and utilities that help with development (especially with writing standard boiler-plate code and scaffolding) but we hope to eventually gain a wide coverage among other tools and technologies (e.g. Python, Ruby, etc.). We are counting on an active engagement from the community to help out in this area.