API World + Integrate 2016

The API pattern was created in the 1970's when 'distributed architectures' didn't even exist and was established mainly for 'centralized architectures' as it bound the communication data/logic to the business logic.

In a modern world, we have moved to distributed architectures where we now have to share the I/O... but that communication logic still remains bound in the application due to an old API pattern. This makes it so that the IO data and functionality related to a request/response cannot be shared with our edge services without duplication/entanglement. This in turn means the data/functionality in our services then cannot be synchronized.
 
This leads to dropped threads, poor security, bad data, bad user experience, broken application, etc.

This can ALL be fixed and improved and even lead to better speed, scalability and automation through a new API Pattern.

In this talk, we will:

- talk about abstracting the API communications from business logic to reduce duplication and improve synchronization
- talk about how this improves automation, scalability and speed
- talk about how you can implement this in your existing infrastructure