The massive growth of APIs and SaaS applications has created a need to integrate anything, anywhere. This integration wave presents unique challenges for organizations looking to integrate both in the cloud and on-premise. Join Ross Mason, Founder & CTO of MuleSoft, as he discusses the emerging hybrid architectures designed to manage this challenge.
In this webinar, you will:
- Hear what the API explosion means to you
- Identify where your integration project falls in the hybrid use case spectrum
- Learn cloud/on-premise integration best practices
- Explore the MuleSoft solution: integrate anything, everywhere
Slide 2: Housekeeping items Just a couple of housekeeping items before we get started: This session is being recorded and will be available immediately following the webinarYou can download the slides right now from the “attachments” tabIf you have content or technical questions, please feel free to ask them at any time by typing them into and sending them via the question button above the slides.We will answer questions at the end of the session but please feel free to send over questions as they arise. If we don’t get to your question or if you have any detailed use-case specific questions, you can submit them to our team of experts at tinyurl.com/askmulesoft
The Social Revolution is also about this incredible shift in mobility. There will be over 1.8 billion mobile devices by 2014 while desktops and laptops are remaining stagnant.Analysts predict Apple will ship fifty-six million iPads shipping this year. Tablets and mobile -- we're in the post-PC revolution now.
Build 1: we never through anything away. Nobody is removing their on premise systemsBuild 2: The amount of data especially unstructured data is creating new challenges for both capturing and publishingBuild 3: Partner and Supplier on boarding is shifting from heavy EDI vans to APIsBuild 4: The first mobility use cases for enterprise have been around enabling the field organizations (engineering, sales, specialist)Build 5: the rise of SaaS applications is entering through the line of business, LoB are also finding ways to leverage public cloud platforms for certain types of apps (testing, LoB bespoke apps)Build 6: understanding the needs of our customers has become the make or break for many companies, this focus has put new importance on reaching and engaging customersBuild 7: Its not only field agents who want access to enteprrise systems, now all employees want to work from their devicesBuild 8: The number of devices are exploding creating new new real time data feeds that can be used to create smarter systems with new levels of engagement and contextGroup by theme (API enablement -publishing)Legacy EnterpriseDataMobilityCloud / SaaSDevices
Build 1: we never through anything away. Nobody is removing their on premise systemsBuild 2: The amount of data especially unstructured data is creating new challenges for both capturing and publishingBuild 3: Partner and Supplier on boarding is shifting from heavy EDI vans to APIsBuild 4: The first mobility use cases for enterprise have been around enabling the field organizations (engineering, sales, specialist)Build 5: the rise of SaaS applications is entering through the line of business, LoB are also finding ways to leverage public cloud platforms for certain types of apps (testing, LoB bespoke apps)Build 6: understanding the needs of our customers has become the make or break for many companies, this focus has put new importance on reaching and engaging customersBuild 7: Its not only field agents who want access to enteprrise systems, now all employees want to work from their devicesBuild 8: The number of devices are exploding creating new new real time data feeds that can be used to create smarter systems with new levels of engagement and contextGroup by theme (API enablement -publishing)Legacy EnterpriseDataMobilityCloud / SaaSDevices
Build 1: we never through anything away. Nobody is removing their on premise systemsBuild 2: The amount of data especially unstructured data is creating new challenges for both capturing and publishingBuild 3: Partner and Supplier on boarding is shifting from heavy EDI vans to APIsBuild 4: The first mobility use cases for enterprise have been around enabling the field organizations (engineering, sales, specialist)Build 5: the rise of SaaS applications is entering through the line of business, LoB are also finding ways to leverage public cloud platforms for certain types of apps (testing, LoB bespoke apps)Build 6: understanding the needs of our customers has become the make or break for many companies, this focus has put new importance on reaching and engaging customersBuild 7: Its not only field agents who want access to enteprrise systems, now all employees want to work from their devicesBuild 8: The number of devices are exploding creating new new real time data feeds that can be used to create smarter systems with new levels of engagement and contextGroup by theme (API enablement -publishing)Legacy EnterpriseDataMobilityCloud / SaaSDevices
Build 1: we never through anything away. Nobody is removing their on premise systemsBuild 2: The amount of data especially unstructured data is creating new challenges for both capturing and publishingBuild 3: Partner and Supplier on boarding is shifting from heavy EDI vans to APIsBuild 4: The first mobility use cases for enterprise have been around enabling the field organizations (engineering, sales, specialist)Build 5: the rise of SaaS applications is entering through the line of business, LoB are also finding ways to leverage public cloud platforms for certain types of apps (testing, LoB bespoke apps)Build 6: understanding the needs of our customers has become the make or break for many companies, this focus has put new importance on reaching and engaging customersBuild 7: Its not only field agents who want access to enteprrise systems, now all employees want to work from their devicesBuild 8: The number of devices are exploding creating new new real time data feeds that can be used to create smarter systems with new levels of engagement and contextGroup by theme (API enablement -publishing)Legacy EnterpriseDataMobilityCloud / SaaSDevices
Build 1: we never through anything away. Nobody is removing their on premise systemsBuild 2: The amount of data especially unstructured data is creating new challenges for both capturing and publishingBuild 3: Partner and Supplier on boarding is shifting from heavy EDI vans to APIsBuild 4: The first mobility use cases for enterprise have been around enabling the field organizations (engineering, sales, specialist)Build 5: the rise of SaaS applications is entering through the line of business, LoB are also finding ways to leverage public cloud platforms for certain types of apps (testing, LoB bespoke apps)Build 6: understanding the needs of our customers has become the make or break for many companies, this focus has put new importance on reaching and engaging customersBuild 7: Its not only field agents who want access to enteprrise systems, now all employees want to work from their devicesBuild 8: The number of devices are exploding creating new new real time data feeds that can be used to create smarter systems with new levels of engagement and contextGroup by theme (API enablement -publishing)Legacy EnterpriseDataMobilityCloud / SaaSDevices
Technical Use CaseLegacy system wrappingService VirtualizationGlobal architectureAPI definition and publishing for device APIsAPI consumption to support SaaS application integrationLead with Application Integration needs a hybrid approachCIO feedback: position as a hybridNeed to be really clear that this is hybrid. On premise and cloud offering. We provide a path to cloud integration There will likely be questions about pricing so we do need to separate the two if that discussion comes upWhere does my integration live? The decision point depends on the locus of the data/apps.
Technical Use CaseLegacy system wrappingService VirtualizationGlobal architectureAPI definition and publishing for device APIsAPI consumption to support SaaS application integrationLead with Application Integration needs a hybrid approachCIO feedback: position as a hybridNeed to be really clear that this is hybrid. On premise and cloud offering. We provide a path to cloud integration There will likely be questions about pricing so we do need to separate the two if that discussion comes upWhere does my integration live? The decision point depends on the locus of the data/apps.
Technical Use CaseLegacy system wrappingService VirtualizationGlobal architectureAPI definition and publishing for device APIsAPI consumption to support SaaS application integrationLead with Application Integration needs a hybrid approachCIO feedback: position as a hybridNeed to be really clear that this is hybrid. On premise and cloud offering. We provide a path to cloud integration There will likely be questions about pricing so we do need to separate the two if that discussion comes upWhere does my integration live? The decision point depends on the locus of the data/apps.
Technical Use CaseLegacy system wrappingService VirtualizationGlobal architectureAPI definition and publishing for device APIsAPI consumption to support SaaS application integrationLead with Application Integration needs a hybrid approachCIO feedback: position as a hybridNeed to be really clear that this is hybrid. On premise and cloud offering. We provide a path to cloud integration There will likely be questions about pricing so we do need to separate the two if that discussion comes upWhere does my integration live? The decision point depends on the locus of the data/apps.
Technical Use CaseLegacy system wrappingService VirtualizationGlobal architectureAPI definition and publishing for device APIsAPI consumption to support SaaS application integrationLead with Application Integration needs a hybrid approachCIO feedback: position as a hybridNeed to be really clear that this is hybrid. On premise and cloud offering. We provide a path to cloud integration There will likely be questions about pricing so we do need to separate the two if that discussion comes upWhere does my integration live? The decision point depends on the locus of the data/apps.
Technical Use CaseLegacy system wrappingService VirtualizationGlobal architectureAPI definition and publishing for device APIsAPI consumption to support SaaS application integrationLead with Application Integration needs a hybrid approachCIO feedback: position as a hybridNeed to be really clear that this is hybrid. On premise and cloud offering. We provide a path to cloud integration There will likely be questions about pricing so we do need to separate the two if that discussion comes upWhere does my integration live? The decision point depends on the locus of the data/apps.
Technical Use CaseLegacy system wrappingService VirtualizationGlobal architectureAPI definition and publishing for device APIsAPI consumption to support SaaS application integrationLead with Application Integration needs a hybrid approachCIO feedback: position as a hybridNeed to be really clear that this is hybrid. On premise and cloud offering. We provide a path to cloud integration There will likely be questions about pricing so we do need to separate the two if that discussion comes upWhere does my integration live? The decision point depends on the locus of the data/apps.
Slide 2: Housekeeping items Just a couple of housekeeping items before we get started: This session is being recorded and will be available immediately following the webinarYou can download the slides right now from the “attachments” tabIf you have content or technical questions, please feel free to ask them at any time by typing them into and sending them via the question button above the slides.We will answer questions at the end of the session but please feel free to send over questions as they arise. If we don’t get to your question or if you have any detailed use-case specific questions, you can submit them to our team of experts at tinyurl.com/askmulesoft