Apis and communications between apps
Communications between different applications/businesses as either the human user or another application. Some business functionallity might need to be split into several apps so that they can managed properly, worked on separately, hide implementation, designed better but they will have to all communicate with one another to provide a business service. This means that apps needs to talk to each other and there are a few ways of doing this.
Versioning
Http/webservices
REST
SOAP
Going to one end point, and the body and/or headers determine how it will be processed
GUI/front end
External source
Ftp/sftp
database
desktop gui
javafx gui
Libraries and frameworks
called with the application
Fixed API to communicate with
advantages?
disadvantages?
others rely on it, it cannot change it is fixed. Otherwise other services may break.
Consumer driven contract testing
stubbing 3rd party apps for testing
Push/Pull
polling/reading
making request regularly
use of scheduled job ie quartz
Ask if there is any new stuff to get on a schedule, then gets it
pushing
app pushes stuff to your app regularly or when new stuff needs to be pushed
Crawlers
form of polling
cover feeds/webpage for info
get data, and then get data from other links
Web sockets
Others
RMI
Hessian
COBRA
Last updated
Was this helpful?