this post was submitted on 26 Feb 2024
15 points (100.0% liked)
Learn Programming
1625 readers
1 users here now
Posting Etiquette
-
Ask the main part of your question in the title. This should be concise but informative.
-
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
-
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
-
Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'd say that heavily depends on Software A and B.
If you want to actively push data from system A, you need to check for system-specific enhancement options for that system. E.g. is there a way foreseen to add custom plugins, call webhooks, etc.
If you want to actively want to pull data from system B instead, you have to do the same exercise as before but for the other system.
Such interfaces (if available at all) are often vendor specific, so one software may use Java for addons, another only Python etc.
In more complex integration scenarios, you often work with a so-called middleware that acts as a translator between different data formats, protocols etc. Such middleware software often already has pre-built triggers or prepared integration routines for very common software. A commercial example that is mostly meant for end users would be Microsoft Power Flow or if you are looking for FOSS you can check out Node Red.
I don't think there is a lot of 'integration knowledge' that is generally applicable independent of the software in use. If you want to start building a toolbox of skills, you could start looking at SOAP, REST, XML, maybe learn a scripting language such as Python etc.
Thanks a bunch for the suggestions. I think learning the basic toolbox is where I should start, then work my way up to the software-specific interfaces.
Have you ran into software made by companies that didn't have APIs available or didn't want their software integrating with other systems? How would you work around that?
For web applications you can often reverse engineer the internal / non-documented APIs using the development tools of your browser or network traffic analysis such as Wireshark. As a last resort for software without APIs you can always use robotics tools and automatically use the GUI as a user would do. You could for example check out the Selenium framework for Java.