{"id":14768,"date":"2016-06-30T22:50:47","date_gmt":"2016-06-30T19:50:47","guid":{"rendered":"http:\/\/www.altoros.com\/blog\/?p=14768"},"modified":"2019-05-07T18:40:05","modified_gmt":"2019-05-07T15:40:05","slug":"building-event-driven-architectures-with-openwhisk","status":"publish","type":"post","link":"https:\/\/www.altoros.com\/blog\/building-event-driven-architectures-with-openwhisk\/","title":{"rendered":"Building Event-Driven Architectures with OpenWhisk"},"content":{"rendered":"
\"JP

JP Genovese, Altoros<\/small><\/p><\/div>\n

Previously, we provided an introduction to OpenWhisk<\/a>\u2014a distributed service for managing microservices. It allows developers to upload event handlers to a cloud service, then registers those handlers to respond to events. At the Austin meetup, Juan Pablo (JP) Genovese of Altoros provided a deeper insight into this platform and event-driven architectures in general.<\/p>\n

To paraphrase a popular saying, OpenWhisk is old whiskey in new bottles, er, containers.<\/em><\/p>\n

That attempt at poetic metaphor having failed, as OpenWhisk<\/a> is indeed a profoundly new way within IBM’s Cloud Foundry-based Bluemix environment to handle event-driven microservices<\/strong>.<\/p>\n

 <\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n