Concept is good. API integration platform and associated abstraction is a good approach. However the description of 'mainframe' connectivity as an example suggests we don't really know what we're talking about over here. It would be like suggesting that we have a plug-in for 'Dell', or 'Solaris' to seamlessly obtain 'Dell data' or 'Solaris data' - get it? Hopefully in the four years since this video was published, some relevant knowledge has been acquired.
Refered a few videos and pdfs but found a lot of marketing talk like the spaghetti integrations diagram... without explaining how it actually reduces the duplicate calls when replaced by an enterprise service bus. The idea of composite apis makes the de-spaghettification so much more credible. Example: 5 apps make One call each to the compositte api instead of each of them making 3 calls to 3 data sources because the compositte api does the job of the 3 calls to the 3 data spurces.
How do you handle the existence of external APIs? Are they part of the System APIs? Or can these APIs be associated directly as part of my api-led connectivity?
Nice video thanks for the overview. I believe I understand the basics of Mulesoft but I don't necessarily agree with the Salesforce on top model. Wouldn't it make more sense to say that all the bottom tier (System API) layer components could talk to each other now because of Mulesoft. Yes Saleforce can take advantage of the new API layer on all the applications but so can any other application. I also have a bit of a concern about combining your system API's in to your process API's. My concern is that you might need to maintain transaction integrity between the System API layer and the Process layer, and I think that it might be difficult to do that. Does Mulesoft offer easy multi system transaction integrity? I mean you enter an order in your accounting system and it succeeds and then you enter your order in your CRM system and it fails. What do you do? I do agree that having this Process API layer makes sense though, just that it will probably be very complex. Now having said that, I would be nervous about building yet another layer on top of the Process layer of API's (Experience) for the reasons mentioned earlier only amplified. I would imagine if I wanted a suite of API's for say our Ecommerce platform I would offer a group of API's together but not one all encompassing API. Just my thoughts though and I am curious to what others are doing. For some of the technical questions and if someone could point me to a place to read up and get these answers I am more than willing to do that. I just think others might have similar questions but didn't ask on this video. Do these API's generated support any type of queuing? Do they support callbacks so that they can work in an asynchronous way? What type of security and monitoring/logging is available? Speaking of logging is there a way to mark attributes of your API as sensitive, so it won't be logged? I am thinking about CC numbers and other PCI data. In your example what if one of the System API's is down. How does that effect the Process layer? Can they support both REST with a JSON payload and also a SOAP/XML? Again thanks for the video and I am not at all trying to be overly critical and apologize in advance if I came across that way in this post. We are considering Mulesoft and I am trying to find out the capabilities of it. Yours was the first video I found.
Yeah but at what price? What’s the return on investment for every 5 developers and licensing arrangements for projects that are riddled with silo oriented intellectual property restrictions? For example, the 5 developers can not connect to those existing system APIs so what kind of financial risks would be incurred to the project if developers have to focus on such work arounds?
Nice explanation man Right now I am working on Oracle SOA suite I am a fresher , I want to how much mulesoft is different from Oracle SOA suite... Will it be difficult for me to move to mulesoft from Oracle SOA suite.?
We are on mainframes and planning to use mulesoft with salesforce. What is the API ineed to install on mainframe. Any usecase or documentation will be helpful. Thank you!
depends on your mainframe :) If you run IBM, i recommend you use zOS connect to expose your business objects, and that you integrate that into Mulesoft through Mulesoft System APIs in front of your mainframe Alternatively, you could connect through (staging) database tables
![[UA] NAVI проти G2 Esports | Blast Premier Fall Final](http://i.ytimg.com/vi/QWlIm4FGESQ/mqdefault.jpg)
I was looking for a brief overview of the platform. This one is perfect. Thanks Eric 😊.
I love this video, thank you, Eric. I attended a Mulesoft webinar during Salesforce days a few days ago and learned a lot
Sir u r too good... i looked out for videos with simple explanation but urs is the best
This explains why Salesforce's Mulesoft acquisition was brilliant
Good to Know that Salesforce aquired the Mulesoft !
Brilliant explanation. Very clear yet informative. Only hope it has higher definition. Thank you.
Went through 20 introductions and this one did the trick. Well explained thanks.
Fabulous visual explanation of the core concepts....I E if the best videos I have seen in digital cxp platform solution area....thanks for this video
This is an extremely helpful architectural view of APIs...and helps in our discussion with clients.
Concept is good. API integration platform and associated abstraction is a good approach. However the description of 'mainframe' connectivity as an example suggests we don't really know what we're talking about over here. It would be like suggesting that we have a plug-in for 'Dell', or 'Solaris' to seamlessly obtain 'Dell data' or 'Solaris data' - get it? Hopefully in the four years since this video was published, some relevant knowledge has been acquired.
Brilliant explanation Eric. Quick and insightful. Thankyou.
An excellent presentation and explanation, thanks Eric !
Refered a few videos and pdfs but found a lot of marketing talk like the spaghetti integrations diagram... without explaining how it actually reduces the duplicate calls when replaced by an enterprise service bus. The idea of composite apis makes the de-spaghettification so much more credible. Example: 5 apps make One call each to the compositte api instead of each of them making 3 calls to 3 data sources because the compositte api does the job of the 3 calls to the 3 data spurces.
Simple and straight forward. I liked the way it was explained.
Excellent video. Clear for beginners!
why do not you add more videos like this Eric. It was good explained! like your teaching style
Great presentation that was clearly explained and I was able to understand.
Thanks Eric for the quick understanding about Mulesoft.
Thanks for this, very helpul!
Great explanation. You made it simple to understand
Thank you Denis - I've been looking for a good overview and yours is perfect. Appreciate the information.
Hi Folks! Are you are looking for Mulesoft certification, ping me for details.whatapp number +918985923088
Great video. Thank you for sharing
Thank You Eric for your support.
Crystal clear explanation. good work really!
Excellent for beginners. Thanks Eric.
Excellent explanation!!
Great video that literally captured the entire concept quickly 👍🏾
Eric, this video is awesome and excellent , Thank you
nice, a very good presentation on Mulesoft concepts. Very helpful 👍
Very well explanation Eric
Hello Eric, great video presentation.
Thank you, this was extremely helpful as a high level overview!
Very Nice explanation. Thank you Eric. Cheers!
Thanks Eric, loved it
Excellent for beginner! Thank you
Awesome explanation. Thanks!
Great video, very much appreciate the knowledge transfer.
Thank you Eric. Great intro
Great video eric. thanks for posting
Thank you for the excellent beginner's explanation!
Hi Folks! Are you are looking for Mulesoft certification, ping me for details.whatapp number +918985923088
A very good explanation of a complex subject...
How do you handle the existence of external APIs? Are they part of the System APIs? Or can these APIs be associated directly as part of my api-led connectivity?
Nice video thanks for the overview.
I believe I understand the basics of Mulesoft but I don't necessarily agree with the Salesforce on top model. Wouldn't it make more sense to say that all the bottom tier (System API) layer components could talk to each other now because of Mulesoft. Yes Saleforce can take advantage of the new API layer on all the applications but so can any other application.
I also have a bit of a concern about combining your system API's in to your process API's. My concern is that you might need to maintain transaction integrity between the System API layer and the Process layer, and I think that it might be difficult to do that. Does Mulesoft offer easy multi system transaction integrity? I mean you enter an order in your accounting system and it succeeds and then you enter your order in your CRM system and it fails. What do you do? I do agree that having this Process API layer makes sense though, just that it will probably be very complex. Now having said that, I would be nervous about building yet another layer on top of the Process layer of API's (Experience) for the reasons mentioned earlier only amplified. I would imagine if I wanted a suite of API's for say our Ecommerce platform I would offer a group of API's together but not one all encompassing API. Just my thoughts though and I am curious to what others are doing.
For some of the technical questions and if someone could point me to a place to read up and get these answers I am more than willing to do that. I just think others might have similar questions but didn't ask on this video. Do these API's generated support any type of queuing? Do they support callbacks so that they can work in an asynchronous way? What type of security and monitoring/logging is available? Speaking of logging is there a way to mark attributes of your API as sensitive, so it won't be logged? I am thinking about CC numbers and other PCI data. In your example what if one of the System API's is down. How does that effect the Process layer? Can they support both REST with a JSON payload and also a SOAP/XML?
Again thanks for the video and I am not at all trying to be overly critical and apologize in advance if I came across that way in this post. We are considering Mulesoft and I am trying to find out the capabilities of it. Yours was the first video I found.
Hi steve, thanks for your comments, if ever you have found information answering to your questions, could you also share them with me? :)
Excellent question, Steve!
the questions remain even 2 years excellent, but I'm still missing the answers... :(
I really want to learn can you help
For all your technical questions, any middleware/integration platform can handle that not only mulesoft
I am the 100th subscriber! Congratulations
Hey Eric, stop at the nearest pub and grab a pint there from me ;). Cheers for the video buddy.
Very well explained 👏🏻
Very well explained thank you!
Thank You Sir it was Fantastic Explanation for us. Regards
excellent presentation Eric
Hello Eric
Great video on Mulesoft for beginners .
How do I learn and work on Mulesoft ?
Please suggest the best way to learn about Mulesoft
nice video. helped me understand api led connectivity
Thank You, nice video!
Yeah but at what price? What’s the return on investment for every 5 developers and licensing arrangements for projects that are riddled with silo oriented intellectual property restrictions? For example, the 5 developers can not connect to those existing system APIs so what kind of financial risks would be incurred to the project if developers have to focus on such work arounds?
New to API concepts so my question is why have multiple layers - Process-Experience etc? How would these help?
Well articulated , worth the time
Amazing! Thank you for sharing
Thanks Eric!
Great explanation!
Nice explanation man
Right now I am working on Oracle SOA suite I am a fresher , I want to how much mulesoft is different from Oracle SOA suite...
Will it be difficult for me to move to mulesoft from Oracle SOA suite.?
I want this for each system I consider to onboard. Its a faster-time-to-aaahaaaa
What should one study if they want to learn more about this topic?
Excellent Explanation
Perfectly explained!!
Just need to know, I'm a mainframe guy. Can I learn mulesoft and how tough will it be for me to learn.
Fantastic. Tank you.
So is mule essentially camel + eip? Seems very similar...
How are these API apps deployed? Where would they run? Like on a app server like weblogic or tomcat?
I am still unclear. So Mulesoft is to create logic flows for existing APIs
Nice video
Thanks, but isn't same thing done by other middlewares
Thanks for Posting
We are on mainframes and planning to use mulesoft with salesforce. What is the API ineed to install on mainframe. Any usecase or documentation will be helpful. Thank you!
depends on your mainframe :)
If you run IBM, i recommend you use zOS connect to expose your business objects, and that you integrate that into Mulesoft through Mulesoft System APIs in front of your mainframe
Alternatively, you could connect through (staging) database tables
THanks!
Thanks you made my day.... :)
Well done!
Well explained.
mule folllows which architecture
thanks eric
Best to watch this video at 1.75X speed. His talking speed is best at 1.75X .
Brilliant Technology
Great !!!
nice.
So its basically apps calling other apps. Who'da thunk it!