Application service architecture

• US 10,277,582 B2
• Filed: 11/19/2015
• Issued: 04/30/2019
• Est. Priority Date: 08/27/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Colle, Olivier, Staples, William James, Aguilar Mares, Carlos, Banina, Samuel Lenz, Anand, Karandeep Singh, Werner, Kyle, Thapar, Gautam
• Primary Examiner(s): Naghdali, Khalil
• Application Number:
  US14/945,626
• Publication Number:
  US 20170063833A1
• Time in Patent Office: 1,258 Days
• Field of Search: 726 9
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 8/31 Programming languages or programming paradigms
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226

Abstract

Described herein are various technologies pertaining an extensible, cloud-based service for creating and executing applications (e.g., business or industry-specific workflows). A user knowledgeable about a particular field can utilize a client-hosted design studio or a web-based portal to create an application (“app”) (e.g., data transform) relevant to the particular field. The system thus enables users to build mobile applications across platforms without having to write computer code to communicate with backend services such as data sources and/or workflow management systems.

Claims

1. A system, comprising:

a processor; and

a memory comprising;

a resource provider configured to, in response to a request to create an application, identify an identified authorized microservice, provide information regarding the identified authorized microservice, and, in response to selection of a selected authorized microservice provide real-time data associated with the selected authorized microservice, the resource provider further configured to store information regarding the selected authorized microservice and metadata describing the selected authorized microservice as the application, the selected authorized microservice associated with a data source, the real-time data associated with a field of data within a schema of the data source to provide a user interface of executing the application while the application is developed.

2. The system of claim 1, wherein the selected authorized microservice is cloud-based.

3. The system of claim 1, wherein communication with the resource provider is based upon a Representational State Transfer based Application Programming Interface.

4. The system of claim 3, wherein the Application Programming Interface is based on Hypertext Transfer Protocol (HTTP).

5. The system of claim 3, wherein the Application Programming Interface is based on Simple Object Access Protocol (SOAP).

6. The system of claim 1, wherein the identified authorized microservice is identified as authorized based upon a token presented in the request.

7. The system of claim 6, wherein the token is a role-based access control web token utilizing a JavaScript Object Notation (JSON).

8. The system of claim 1, the application is created without a user writing code.

9. The system of claim 1, wherein the metadata further comprises a sharing attribute.

10. The system of claim 9, wherein the sharing attribute is indicative of whether the application is sharable across a tenant boundary with a different tenant of a cloud-based provider.

11. A method, comprising:

providing information regarding one or more authorized microservices for which a user is authorized;

using a Representational State Transfer based Application Programming Interface, receiving information regarding selection by the user of one or more of selected authorized microservices of the one or more of authorized microservices for which the user is authorized;

providing information regarding data associated with the one or more selected authorized microservices, the one or more selected authorized microservices associated with a data source, the data associated with a field of data within a schema of the data source; and

storing information regarding the one or more selected authorized microservices as an application along with metadata describing the one or more selected authorized microservices to provide a user interface of executing the application while the application is developed.

12. The method of claim 11, wherein the data is real-time data associated with a particular data source.

13. The method of claim 11, further comprising:

authenticating the user, the user having role-based access authorized control to the one or more authorized microservices.

14. The method of claim 11, further comprising using a Representational State Transfer based Application Programming Interface, receiving logic for transforming data for the application.

15. The method of claim 11, further comprising using a Representational State Transfer based Application Programming Interface, receiving a visual for the application.

16. The method of claim 11, further comprising using a Representational State Transfer based Application Programming Interface, receiving information regarding sharing of the application.

17. A method, comprising:

using a Representational State Transfer based Application Programming Interface, receiving a request for gallery items;

identifying identified authorized applications associated with the request;

providing information regarding the identified authorized applications;

using a Representational State Transfer based Application Programming Interface, receiving selection of a particular identified authorized application of the identified authorized applications; and

providing a package of the particular identified authorized application to provide a user interface of executing the particular identified authorized application while the particular identified authorized application is developed.

18. The method of claim 17, wherein the package is a file comprising HyperText Markup Language.

19. The method of claim 17, wherein the package is a file comprising JavaScript.

20. The method of claim 17, wherein identifying authorized applications associated with the request is based on a token received with the request.