API projects — microservices

• Enables combining multiple internal APIs into a single external API
• Supports parallel execution to improve performance
• Supports Mainframe, IBM i, databases, SAP, SOA, REST through screens, programs or data layers
• Generates highly customized standard Java code
• Supports transactional operations over multiple data sources
• Orchestration projects are also known as API projects or microservices

Fields to be defined:

• Microservice Project — checkbox
• Project Name
• Default Package — auto-populated from Project Name
• Use Custom Project Template — checkbox
• Service Type — endpoints list

Orchestration project types

Orchestration projects can be categorized into two groups: top down (contract first) and bottom up (contract last). The differences are in how they are created, not in the end result.

Top down (contract first)

Used when the requirements for the output of the project are clearly defined (a well-defined API). For example, a business analyst has defined the requirements for a customer invoice — what fields are required, what data needs to be calculated — and the project creator can identify the sources: customer information from Database A, item information from Inventory system C, and so on.

Bottom up (contract last)

Used when the specific outputs are not well defined, or when the legacy resources will be used for multiple purposes (multiple outputs).

Endpoints

Although the most common endpoint used in API and microservices projects is REST, the OpenLegacy platform supports multiple endpoints.

See Service project and Migrate to Core 5.2.0 (Spring Boot 4).

---

Source: API Projects - Microservices (Confluence)