This video explains: 1. What is API LED Connectivity ? 2. What are System API, process API and experience API ? 3. When to go for System API, process API and experience API ? 4. Advantages of API LED Connectivity
Hi Friends, Looking for complete course to learn mule ESB with real time scenario's ? It is available in udemy : www.udemy.com/course/mule-4x-indepth-beginner-to-expert-with-real-time-use-cases/?referralCode=93AA87E9E68C1DE40F09
Hi chinna garu , Thank you for the wonderful explanation. Your videos are more than a blessing for the mulesoft job seekers. I really mean it. The time you are spending in explaining the concepts is just amazing. I have a small request, Just want to check if there is any possibility for you to provide real time projects training..
Hi Sir, you are taking the examples of SAP and SALEFORCE. But from bachend Java technology . We can retrieve XML format from different type of Host in Mainfrane. We can use some third party JAR files to connect. So, by using MuleSoft how can we achieve. From which connectors need to use. Can you plrsse make on DIGITAL BANKING APPLICATION THAT SUPPORT MOBILE. Thanks.
Thank so much sir.. I have a system api which talks to a web services and gets response. I need a api to give to multiple clients with different format of response . So can I develop one system api and one experience api ?? But I am confused how can I give a experience api to multiple clients as they all need different format , can I get a username from query parameter and response back based on user ?? Or any other best way to do it ?? Please suggest ,,
good tutorial. can you put some real usecase on api led how to call them from one layer to other and how to do error handling. which will help many people
Hi Chinna, These are really good videos for beginners. I have one question on Experience API. Can we say that Experience API are API which are build for dedicated clients? And Process API and Experience API are same if we have only single client? Please correct me if I am wrong.
Thanks for knowledge sharing... These videos are very useful for mulesoft beginners Can you guide me, I am from middleware admin support background. Can I learn mulesoft. Is it required more java Development skills?
Hi Srinu, You can learn mule. You don't need much java knowledge, i would suggest you to complete this course then try to learn core java if possible. I believe you have some idea on java from college. So that is enough to learn mule.
Hi Sir, API Led connectivity explanined very well, thank you. i am having a doubt, the way API led connectivity is explaned for fetching data using get method, please can you elbroate on post method is API Led connectivtiy. Hope my question is clear if we are posting data from portal to salesforce how API led connectivity will work. thnak you,
You can have a POST based rest service in system API (salesforce dedicated) which takes input expected by Salesforce object and do insert. Make sure you should not do any enrichment's in this system API where as process API should do all necessary transformations and enrichment's then call system API. But go for system API if and only if that is reusable.
Assuming the system APIs return data in size of 1lakh for example. And we are doing some data transformation and enrichment in process API level. Now to reduce the response time in experience APIs, is it a right way to do the following? 1. Collect data from system APIs by a scheduled process API, that will enrich and save data in a database. 2. When experience APIs will request data, the process APIs return data from the database where they have the transformed data?
Hi Bibek, If you would like to deal with 1 lakh of records then API LED Connectivity won't be feasible because we can not communicate huge amount of data over request reply pattern. Go for batch processing when you would like to deal with huge amount of data. As per your question If less amount data can be transferred over request reply using HTTP then API LED Connectivity won't save any time because process API and system API takes same time to do ETL. An API can be able to deal less amount of data transfer over HTTP with request reply pattern. You will not get performance level improvement by API LED Connectivity where we can get re usability and micro service features by API LED Connectivity. I would suggest you to watch the session again and let me know if you have any questions. Thank you. Keep learning.
This is not at all a microservice if we follow this approach. Example: all database filter operations on employee database will need to be used in one sapi, that means all the services are combined here(each filter means one business use case)
