Development Guidelines

Development Guidelines

The various IT departments within the company often do not have a uniform approach to training squad teams and IT employees, or to conveying the same IT vision. That’s why effective API Orchestration design, keeping Service Oriented Architecture portable for the future and a short time to market are important.

Development and Training by Rivium developers focuses on uniform working methods and iSmart Orchestration.

Simplification of API registration:
Registration of the interface purchaser together with the expected workload must be supplied in Git version control to enable generation of API workload estimates as a prognosis for increased CPU/memory requirements.

Agility:
Clear registration of User Stories in an issue tracker for both business and IT employees in the squad.

Workload:
Real-time production environment statistics are needed for capacity management.

Real time:
Documentation with fewer manual revisions results in increased business value. Your development team wants to create business value, not documentation.

Simplification of ESB architecture:
Standard guidelines for service-oriented architecture and TIBCO BPM; your ESB interfaces must meet standard WSDL registration guidelines in Git version control.

Generic regression tests:
Your interfaces must meet standard WSDL/XSD registration guidelines in Git version control to enable regression test generation in SOAPUI or JSON.

API UI standard guidelines:
For the best UI application user experience, you need a central library with reusable UI templates so that you can concentrate on improving your business process.

API LCM standard guidelines:
In order to ensure a high degree of availability, your life cycle management and patch management for middleware must be directly translated into user stories by a central PaaS middleware team for their backlog.

API scalability:
Virtualization and standard guidelines for dual-node configuration for 24/7 availability in your OTAP process and flexibility for scaling up your interface to one microservice implementation per customer.

OpenSource projects for scripts:
For Continuous Integration/Continuous Delivery and version control, OpenSource tooling is preferred over vendor tooling to guarantee reusability, compatibility and portability for all customer legacy systems.

Learn more about Development Guidelines?

Contact us