Augmenting Existing APIs With Event-Driven Architecture
More APIs are moving towards an event-driven way of doing business. Meaning instead of just responding to requests made to the API paths, they respond to events that occur in real time and to schedules, pushing and streaming data to when and where they are needed. Event-driven approaches to delivering APIs are more efficient and help applications reduce the noise and chattiness that can often be present within active platforms. Helping make platforms better serve end-users and ensuring our API-driven applications respond with more meaningful interactions and the signals that matter to users.
The biggest challenge with the event-driven evolution across the API sector is not all API providers are to the place in their journey where they see the importance of an event-driven approach or have the resources to begin investing in the infrastructure that is needed. Putting the burden on API consumers to do the heavy lifting of sorting through the noise, polling existing endpoints for relevant signals, and making sense of what is happening. Luckily, there are ways in which we can help API consumers better optimize the API infrastructure they depend on from the outside-in, augmenting existing APIs with the event-driven architecture that is required. https://goo.gl/kgiaz2 #DataIntegration #ML
Considering Event-Driven Opportunities Around the Tableau Extensions Dashboards
#ICYMI: We are learning more about the Tableau Extensions API and the extension gallery they’ve just published. It allows developers to create dashboard extensions that enable Tableau customers to integrate data from other applications into Tableau. Some of the use cases Tableau provides for extensions are:
*
Create an extension that has write-back functionality so users can modify data in a viz and have that change automatically and update the source data in the database or web application. https://goo.gl/1QfqKB #DataIntegration #ML

