IPFS nodes allow you to access them over an HTTP API. The API ensures that both IPFS core implementations and their respective HTTP client libraries offer the same interface, so that developers can quickly change between a local and a remote node without having to change their applications.
Use whatever resources available to you, in order to come up with a visual representation of the topic that can be projected on to a poster (similar in spirit to the poster description but with whatever creative freedom your group prefers :^)
- What applications target this API?
- What are the benefits of having a consistent API across languages?
- Are there alternatives to HTTP that offer the same interface?
https://ipfs.io/docs/api/
https://github.com/ipfs/interface-js-ipfs-core
https://github.com/ipfs/go-ipfs-api
https://github.com/ipfs/js-ipfs-http-client
https://github.com/ipfs/go-ipfs-http-client