IT teams are always wanting to build new applications enabling specific functions for the ease of processes or customers. Sometimes, to balance projects, they allow distributed teams to work on focused targets using reusable assets, templates, and best practices. While decentralizing and democratizing application development helps, managing security can be a task for strategizing different Lines of Business (LoBs) and functional business partners. Enter microservices.
Resources Sample File: MicrosoftGraphTemplate.lsoz (65.8 KB) (download) API Reference: More information on the specifics of authentication can be found in the Microsoft Graph API reference documentation. Microsoft offers a RESTful web service named Microsoft Graph API. This tutorial shows you how to integrate with the Microsoft Graph API and Linx, a low-code development tool.
Using a low-code platform as the back-end for a single page application (SPA) is a nice combination — the SPA can be hosted anywhere, the API is quick and easy to develop, and they can evolve independently of each other e.g. if you need a native app just develop the UI and use the same API.
SOAP, being a mature technology, has an extensive and often differently interpreted standard set. This makes it an excellent tool for corporate users to manipulate data into their precise requirements and technology stack. However, for public consumption, this causes issues that sometimes are difficult or impossible to solve without changing code. A good example here is that SOAP is allowed to define the same type in some standard interpretations in different XSD files.
Companies acquire enterprise SaaS applications (such as Microsoft Dynamics, Salesforce, ServiceNow or Workday) to accelerate business capabilities. However, the complexity increases as businesses begin to customise and integrate solutions to suit their business requirements. So, the cost of overlooking testing the application can be catastrophic in the form of monetary and reputational damage.
