SaaS Deployment Architecture

In this scenario, all AppDynamics services run as SaaS, and agents are configured to talk to the public SaaS endpoints. For EUM, by default, we resolve end-user locations using public geographic databases.

Although not strictly required, we recommend using a reverse proxy such as NGINX or Apache for all server-side components.

Note

Components must be licensed separately.

Figure 4-4 illustrates a SaaS AppDynamics deployment architecture.


Figure 4-4 SaaS AppDynamics deployment architecture

Figure 4-5 illustrates the connections, datastores, and key for the SaaS deployment architecture.


Figure 4-5 Understanding SaaS deployment architecture

In the next sections, we review the various monitoring capabilities in AppDynamics.

Application Monitoring

AppDynamics Application Performance Monitoring (APM), a component of the AppDynamics platform, provides end-to-end visibility into the performance of your applications.

AppDynamics works with popular programming languages such as Java, .NET, Node.js, PHP, Python, C/C++, and more, enabling you to do the following:

• Troubleshoot problems such as slow response times and application errors.

• Automatically discover an application’s topology and how components in the application environment work together to fulfill key business transactions for its users.

• Measure end-to-end business transaction performance, along with the health of individual application and infrastructure nodes.

• Receive alerts based on custom or built-in health rules, including rules against dynamic performance baselines that alert you to issues in the context of business transactions.

• Analyze your applications at the code execution level using snapshots.