“MicroFlow” mean the EMF Service instance that consists of a runnable micro service with main purpose of inter-connection and information flow between other MicroFlows or customer micro services, softwares ,SaaS and other information services.
Each MicroFlow consist of
i) an API with 1-N services exposed
ii) an implementation of logic called through the API
iii) a set of outbound calls “references” to 1-M other services
Each MicroFlow may not be
1. directly dependent to more than one (1) outbound system call.
Purpose is to limit the dependency complexity of a single MicroFlow.
Note that each MicroFlow can call an unlimited number of other MicroFlows
2. consuming more than one (1) Amazon EC2 compute unit.
If the performance is not sufficient another Flow is activated.
A customer may choose one of two strategies in MicroFlows
a) Large services – with wider APIs, heavier logic & more references
b) Small services – with smaller APIs, smaller logic & less references
The number of MicroFlows, the selected service level and the performance/capacity required is the main drivers in the fees of the EMF service. In order to reach the long terms goals of reuse and organizational agility Entiros recommend a sound structure with division of MicroFlows in
- layers with MicroFlows for channels, processes and systems
- logical purpose with MicroFlows for each channel, process and system
- operational purpose with MicroFlows for each zone, environment, geography
Questions or Additional Information: If you have questions regarding this Agreement or wish to obtain additional information, please send an e-mail to firstname.lastname@example.org
The customer specific MicroFlows produced - and put under support as defined in this agreement – are under the terms stated in “Entiros General Terms”
The customer specific MicroFlows are the asset of the customer - after direct or indirect acceptance test by customer followed by Entiros delivery of the MicroFlows. Any non-customer specific MicroFlows, that are not explicitly delivered to customer as part of Entiros delivery process, are not the asset of the customer but at the ownership of Entiros.
If customer shall decide to leave the EMF service - from other cause than agreement breach by customer - the MicroFlows necessary to maintain operation of customer service will be made available to under open source contribution license CPAL 1.0 https://opensource.org/licenses/CPAL-1.0 but NOT further supported by Entiros. This include specifically the ManagmentFlows (error handling, logging, monitoring etc.) utilized by customer as part of the EMF service.