After MuleSoft published the paper "API-led connectivity" some years ago, lots of companies have embraced it. However, Mule developers sometimes create too many pass-through APIs that just do not add any value. In this session we are going to explain when we think it is ok to create just an API and when it makes sense to create multiple layers.
Cognizant
Senior Manager
Senior Manager at Cognizant - MuleSoft Ambassador - Integration Architecture. International career working on digital transformation projects in areas such as Integration, API Strategy, Cloud, Microservices, SOA, CRM, and ECM. Outstanding English skills (IELTS exam, score: 7.0). Projects in Germany, UK, Argentina, Spain. Alumni of IESE (Forbes Ranking #5 of MBA Business Schools).
EPAM Systems
Senior Solution Architect III
Accenture
Application Developer
Currently working with Accenture as Application Developer. Having 4+ yrs of Experience in MuleSoft. Worked on Multiple projects as connecting, transforming, integrating, and providing synchronization to multiple systems, API's, DB's. As of now, I am all MuleSoft Certified Developer/Architect, an Active MuleSoft Mentor and MuleSoft Meetup Leader for Surat and Bangalore Chapters.
EPAM Systems
Principal Architect
Accenture
Consultant/Application Developer
