Appian: Standard FAQ’s

Why Appian?

Appian is best when you need to build business application fast, especially when work involves: processes, workflows, automations & Integrations

1. Low-code development.
2. Pre-built components/plugins
3. Automated deployment pipelines
4. Future Ready scalability
5. Built-in intelligence & Automation

How to create Memory efficient Models:

1. Record centric applications
2. Modular Design with Sub-processes
3. Handling Asynchronous Integrations.

Why Appian going to Kubernetes

One unified architecture for cloud & self managed. Appian is standardizing its platform so that Appian cloud & Self-managed customers run on the same Kubernetes-based architecture.

Key features:

1. Easy to manage
2. Automatic scaling
3. Self-healing infrastructure
4. Load balancing
5. Store orchestration &rolling updates.

When to increase application server/engine replicas

1. High Java Work queue size → Increase application servers
2. High “Other Time” in engine summary → Add engine replicas
3. Low Idle time in engine performance logs → Add execution/analytics shards.

Appian scaling: Considerations When Determining scalability.

1. Number of concurrent users.
2. The average number of requests per user.
3. The average size of each request.
4. The size of the machine the platform is running on.