Upgrade to Pro — share decks privately, control downloads, hide ads and more …

A Look Back at Enterprise Integration Patterns ...

Bruno Borges
February 22, 2018

A Look Back at Enterprise Integration Patterns and Their Use into Today's Serverless Computing

Functions, and the so called serverless computing have freed deveopers from worring about infrastructure, and even upper platform layers, as well some steps in the software development lifecycle. But once you have functions deployed, how do they interact with each other? How message navigates between them? Maybe, just maybe, it’s time to look back again at EIPs - Enterprise Integration Patterns, and their use in this new way of deploying code to the Cloud. This talk will cover primarily the use of one of the key EIP frameworks - Apache Camel - and top patterns applicable to Serverless Computing using Functions services by Cloud vendors as part of the demonstrations.

Bruno Borges

February 22, 2018
Tweet

More Decks by Bruno Borges

Other Decks in Technology

Transcript

  1. Existing Application APP Modern Microservices Add new services or start

    peeling off services from monolithic code. Modern Methodologies Implement CI/CD and automation. Modern Infrastructure Move to the cloud as VMs or Containers or refresh HW. Containerize Applications Re-architect apps for scale with containers.
  2. 23 February 2018 @brunoborges / @azureadvocates I have no life,

    that’s why. Give me SSH! Just run my container. I don’t give a damn anymore. Here’s my code!
  3. Azure Functions On-demand serverless code Java Suport via an SDK

    and in VS Code CI/CD support in Github and Visual Studio Team Services
  4. Serverless code execution on Azure HTTP Request Timer Storage change

    IoT Event CRM record update Tweet on Twitter + 100’s more event sources…
  5. 5) Output binding Azure Services 7) Develop locally 6) Monitor

    and improve 3) Develop 4) Execute 2) Input binding Web Hooks 1) Trigger Azure Services 8) CI/CD Seamless Dev experience with Functions Extension
  6. 23 February 2018 @brunoborges / @azureadvocates 0 20 40 60

    80 100 0 2 4 6 8 10 12 14 Integration Points Complexity
  7. 23 February 2018 @brunoborges / @azureadvocates RouteBuilder builder = new

    RouteBuilder() { public void configure() { from("direct:a") .filter(header("res").isEqualTo("low")) .to("direct:b"); } };