API Architecture Deep Dive - Architecture Decisions for Integration Systems
ฝัง
- เผยแพร่เมื่อ 6 ก.พ. 2025
- This video explains how to think about API Structure and Architecture while Designing any Integration Platform. These decisions play a major role during the 'Design' and 'Development' phases and largely avoid rework and redesigning once the implementation is completed.
These are common principles and guidelines and not Thumb Rules. The Architecture of the Integration Systems need to be flexible for the specific use-case scenarios and depends on the different APIs that will be developed and used under the organization for the significant time duration.
If there are any doubts, questions or clarifications on the Architecture or related topics, please feel free to add your questions in the comments section, I will try to clarify.
Happy Learning !! Cheers !!
Thank you for the guidelines! Very insightful!
Thank you for the concise and well summarised important design process
thanks for sharing
such a great piece of knowledge.
Good guidelines. Thanks
Awesome Sir Ji.. Please write practical based book.
Hi Gitesh - Thank you. I am planning to start the series of Blog pages where my videos can be embedded and can be with more textual explanation with sample piece of code. But it will take time and will start that next month. Thanks for your feedback.
@@sivathankamanee-channel Thanks Siva for your quick reply and All the best for your invovative series..
Hi Siva, I have a quick question. We have enabled External Identity which means we can't use username and password for login or deployment. Now if we want to implement CI/CD then how can we deploy our apps?
Hi - Please create an application with the external identity and disable multi-factor authentication so that the CI/CD can just use Client credentials token without the need of giving user credentials at real time.
we have any mule project. please send me mule project