<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

Best Practices for Building and Managing Microservices

Many cloud providers now provide what are called "functions as a service." Azure cloud offers Azure functions, and Amazon offers Amazon functions.  Your company may also wish to provide its own REST-based services that perform server-less computing and the purpose of this essay is to review the basics of how to maintain, manage versions, and ensure optimal performance of our REST-based Microservices.

API performance improvements using server and user sessions

API's are the primary way to access most applications. And as applications become increasingly feature-and-function-rich, their API can become more complex and impact performance.  Workflow applications evolved in this exact way:  when they were rudimentary then their APIs were small and there were few issues - but as features and functionality were added, API performance degraded noticeably. 

FlowWright low level API model

FlowWright has 2 APIs, high level and low level, as you know the high level API gives you access to everything withing FlowWright.  cDevDEAPI is the high level API.

FlowWright high level API model

The FlowWright high level API is the main API for all FlowWright components, user interface, business logic, engines and gives all access to functionality and objects within FlowWright.  The API is divided into parent/child objects as described below:

FlowWright v9.3.0.2 Maintenance Release

FlowWright is happy to release the maintenance release for v9.3. This maintenance release contains the following enhancements and fixes: