Abstract: In a provider network, a developer console generates web pages defining a developer portal for transmission to web browsers. An application architecture modeling service analyzes developer interactions with services executing on the provider network to allow the developer to create an application. From the developer interactions (e.g., API calls, click stream data), the application architecture modeling service dynamically determines a model of the architecture of the application and updates the model as the developer continues to further interact with the developer services. The web pages generated by the developer console are encoded to contain graphical images of the application's model including hyperlinks.

Abstract: A service provider network offers various services to users. Some of the services may be stateless services. Data flow tokens may be generated and embedded in packets that are provided to the various services. A data flow token uniquely identifies the data flow for a set of services that are invoked by, for example, an application programming interface (API) call to the service provider network. The various services that are invoked as part of a common data flow write diagnostics data to a diagnostics log service. The diagnostics data may include the data flow token as well as a time stamp when the service was invoked and a time stamp when the service completes. The time stamps can be used to determine the period of time that the service took to execute. Analysis of the execution times can assist in, for example, auto-scaling the services for better performance.

Abstract: Merging data from LOB applications into document templates within productivity applications without the need for custom programming is provided. A document template within a productivity application is provided, and an XML schema is attached to the document template. The XML schema allows the LOB application data to be modeled generically using a business object paradigm. Meta-data is accessed from the LOB application. Using the attached XML schema, a user may mark-up the document template with schema nodes corresponding to the meta-data from the LOB application. Data from the LOB application may then be accessed and merged into the schema nodes, creating a data-merged document. Data may be further interactively merged from the LOB application into the data-merged document.

Abstract: Merging data from LOB applications into document templates within productivity applications without the need for custom programming is provided. A document template within a productivity application is provided, and an XML schema is attached to the document template. The XML schema allows the LOB application data to be modeled generically using a business object paradigm. Meta-data is accessed from the LOB application. Using the attached XML schema, a user may mark-up the document template with schema nodes corresponding to the meta-data from the LOB application. Data from the LOB application may then be accessed and merged into the schema nodes, creating a data-merged document. Data may be further interactively merged from the LOB application into the data-merged document.