User Events Across a Platform as a Common Event-Driven API Play
We’ve talked about how the presence of webhooks as part of API operations is usually the first place platforms begin investing in event-driven API architecture. Another common pattern we are seeing as we continue to study the event-driven approach of API providers is a user events API, providing an API for accessing, webhooks for subscribing, and real-time APIs for accessing all the events that occur across a user’s account. Providing a single place to tune into all the meaningful events for a user, or potentially a group of users, of a platform.
You can see an example of this in action over at the document storage API platform Box, with their events API endpoints which, “provides an API endpoint at /events that presents a stream of two different types of events, called user events and admin events. Admin events are those events that are retrieved when you request a stream_type of admin_logs. User events are all other events.” Here is a list of the events they are providing access to: https://goo.gl/pEMd5D #DataIntegration #ML
Overview of Spark and HTTP Testing With JUnit
ICYMI: TLDR: Spark is static so having it run in an @BeforeClass allows HTTP request testing to begin.
I use Spark as the embedded web server in my applications. I also run simple HTTP tests against this as part of my local Maven build. And I start Spark within the JUnit tests themselves. In this post, I’ll show how. https://goo.gl/53qmXM #DataIntegration #ML
