Development
Systems come and go and as the business evolves there is always a need for new integrations or adjustments to existing ones. The greatest challenge is to manage complexity and to be able share and communicate with various stakeholders. Here is the process for architecting new fail-safe integrations.
1. Integration landscape analysis
Starting with a clear picture of the entire integration landscape is the best possible way to make decisions about developing new integrations. IT architects can use the Nodinite repository, where all integrations are documented in detail, as a starting point. The repository can later be updated as needed.
For more information on how it works, see:
Repository Model | Nodinite Docs
2. Collaboration
The integrations, new or existing, are discussed, shared, and developed in collaboration between the right people in order to be developed as quickly as possible.
3. Development and testing
Develop your integrations on any technology, e.g. Azure, Boomi, IBM, MQ, etc. Using the design in the repository as your guide. To help your IT operations maintain control over the integrations and related business message flows, it is recommended to write knowledge-based articles in the repository, such as on how to deal with specific problems. These articles will be published and are readily available in the monitoring views. This is a real time saver.
2. Collaboration
The integrations, new or existing, are discussed, shared, and developed in collaboration between the right people in order to be developed as quickly as possible.
