Enterprise Mobile App Architecture Explained

The Differences Between Enterprise and Consumer Mobile App Architecture

When looking at Enterprise Mobile Applications and Consumer Mobile Applications, the first thing that stands out is the number of users; enterprise applications may have hundreds of thousands or even millions of users while consumer applications generally have thousands to tens of thousands of daily active users.

An enterprise mobile app will also have multiple backend systems, which need to be integrated and accessed by the end-user in a secure manner. In addition to this, the enterprise mobile application will typically have a longer lifecycle than that of a consumer mobile application (generally measured in months or years instead of weeks). Also, there are typically many different teams that would touch the same system in an enterprise environment versus a consumer environment. Therefore, how an enterprise architect designs an enterprise mobile application is much more important than simply the features, frameworks, or UI design.

The enterprise mobile application architecture consists of the structural framework used to build an enterprise mobile application. It includes how the application communicates with the back-end applications, how the back-end applications manage and store data, the way that the application protects user data and secure users, how the application supports an increase in users and traffic, and lastly, how it can be maintained and evolved over time to meet the needs of the enterprise.

Filtering through to the components that make up the enterprise architecture will help to define how an enterprise mobile application will evolve, integrate with other enterprise platforms, and scale, as those platforms grow.

Core Principles – Enterprise Mobile App Architecture

Prior to defining enterprise mobile application architecture components, it is important to understand the principles that guide how enterprise-level designs are created.

1. Separation of Concerns

The mobile user interface and business logic should remain loosely coupled from the back-end services.
This allows teams to develop independently, but they can still work with and connect to other teams in the global production system.

2. Scalability by Design

As with many forms of enterprise level solutions, enterprise level apps will grow. Therefore, enterprise architecture must be scalable horizontally throughout the globe, regardless of the user, region or device you are referring to.

3. Security First, Not Last

Authentication, authorization, encryption, auditability, etc., should be built into and designed into the enterprise architecture, not added at a later stage.

4. Integration Friendly

Enterprise applications do not stand alone; they typically connect and integrate with ERP, CRM, data warehouse, identity provider, and legacy systems.

5. Observability and Control

The architecture of an enterprise mobile application must include the ability to monitor, log, analyse and govern the entire application through the architecturally integrated components of the enterprise.

Enterprise Mobile Application Architecture Overview from a Top Viewpoint

From a top level, enterprise mobile application architecture can be broken down into five layers:

• The Mobile Client Layer
• The API & Integrations Layer
• The Backend Services Layer
• The Data & Infrastructure Layer
• The Security & Governance Layer

Each of these layers has a unique purpose and a failure in any layer will cause issues for all layers.

1. Mobile Client Layer (Frontend)

When it comes to enterprise mobile applications, the choice is generally between:

• Native applications for performance and control over the platform (i.e. iOS or Android)
• Cross-Platform applications that enable you to develop more quickly and share the business logic.

From an architectural viewpoint, the framework does not matter, the amount of logic that exists on the device does.

Best practice models for enterprise mobile clients include:

• Thin clients – the majority of logic exists on a server and only the presentation/UI and Local State exists on the device
• Limited Business Logic – No or minimal business logic on the device
• Server Driven Configurations – provides flexibility through the configurations available to the server
• Using Features Flags Control for the rollout of specific features available to the client

Enterprise Mobile Client Must Support:

• Offline access and synchronization capabilities
• Differences in device capabilities
• Backward compatibility for devices
• Controlled uptimes for applications to prevent users from being surprised by the release of new capabilities.

2. API & Integrations Layer

As previously discussed, the API & Integrations layer is the most critical component of an enterprise mobile application’s architecture.

The API is more important than the Mobile App – Enterprise Mobile Applications can be considered as clients that leverage APIs.

1) API Layer

• a) It abstracts and hides complexity in back end systems
• b) It provides protection of the back end core system
• c) It allows for versioning and continued evolution of a back end system
• d) It controls access to the system and rate limits access by clients
• e) It allows for supporting multiple types of clients other than just mobile devices

2) Patterns Commonly Used In Mobile Backends:

• a) REST and GraphQL APIs
• b) API gateways for routing and providing security for APIs
• c) The Backend-For-Frontend (BFF) pattern
• d) Service orchestration for complex workflows

3) An API Layer allows mobile apps to remain steady and reliable while back end systems change.

4) Backend Service Layer

Monolith vs Microservices in the Enterprise

Enterprise mobile backends go through a progression of stages in most enterprises:

• a) Initially centralized service model
• b) Service model gradually evolving to break out domain-based services.
• c) Market Forces of Cloud Technology and the rise of Event Driven Architectures enabling scale.

Key Considerations in Backend Architecture:

• a) Service boundaries should be aligned to the business domains of the enterprise.
• b) Backend Services should be stateless to allow for returnable requests for scalability.
• c) Multiple teams are responsible for different services, meaning clear service ownership for a specific service or domain should be placed with a specific team.
• d) Mobile clients should maintain backward compatibility with prior versions.

The Backend Service Layer Supports the Following:

• a) Providing Business Rule Logic
• b) Compose the Workflow
• c) Generate Notifications
• d) Aggregate Data
• e) Integration of External Systems

5) Data and Infrastructure Layers

• a) Data Architecture and the Data Used by Enterprise Mobile Applications
• b) Data Types Used by Enterprise Applications

Transactional Data, User Profiles, Operational Data, Analytics, and Telemetry

Architectural Best Practices:

• a) Have separate Operational Data Stores and Analytical Data Stores
• b) Provide Read-Optimised APIs optimised for Mobile Application Performance
• c) Have caching layers to limit data latency
• d) Replicate Regional Data in Multiple Regions, for End Users Globally.

6) Enterprise Mobile Infrastructure

Enterprise Mobile Back End Infrastructure should provide auto-scaling, high availability, and disaster recovery for multi-regional deployments.

Infrastructure is a direct input into the App’s Performance and Responsiveness, Downtime Risk and Operational Cost.

Components of Core Security

• Identity Management and Access Control
• Authentication by Tokens
• Authorization based on Role
• Key Management that is Secure
• Data Encryption that is End-to-End
• Mobile Apps & Their Services Should Meet Certain Enterprise-Specific Requirements
• Such as: Compliance with applicable Industry Regulations
• Auditable Trails of User Actions
• Device Level Security Controls
• Secure Distribution of Mobile Applications
• Enforcement of Policies

Enterprise Mobile Application Architecture is assumed to have a Zero Trust Model where Devices may be Utilized Outside the Corporate Network.

Mobile Applications Should Follow the Below Patterns of Enterprise Mobile Application Architecture

1. Backend for Frontend (BFF)

This pattern has a Dedicated Back End designed specifically for Mobile Devices, which will:

Consolidate Data from Several Different Services.

Minimize Network Calls.

Minimize Payload Size.

Hides Mobile Clients from Changes to the Backend Service.

2. Event-driven Architecture

This architecture pattern is used when Mobile Applications Require Real-time Updates, Systems Should Have the Ability to Scale Independently, Business Processes Flow Through Many Different Services and Events Will Decouple Systems, Increasing Resilience.

3. Modular Architecture

The Frontend and Backend of Mobile Applications are Organized as Modules:

• Feature Based Modules
• Independent Deployment
• Clear Contracts between Each Module
• This will increase Maintainability and velocity of Teams.

Considerations of Performance When Developing Enterprise Mobile Applications

Most performance problems stem from Architectural issues, not from issues with code.

The Most Common Causes of Performance Problems:

• Chatty APIs
• Backend Services Being Overloaded
• Lack of a Proper Caching Strategy
• Excessive Processing on the Client Side
• Poor Data Synchronization between Client and Server
• Enterprise Solution Focuses on:
• Minimizing Network Calls
• Aggregation Server-Side
• Predictable Response Time to Client Requests
• Graceful Degradation Under Load

Scalability Issues Related Specifically to Enterprises

Enterprise Mobile Apps Scale:

• Users
• Departments
• Regions
• Devices
• Use Cases
• Architecture Solutions For These Scalable Issues Are:
• Scaling Back End and Front End Services Horizontally.
• Load Balancing at Multiple Levels of the Architecture.
• Executing Processes Asynchronously.
• Employing Global Content Delivery Networks.
• Implementing Data Partitions.

Scalability Must Be Planned; it Cannot be Patched.

Enterprise Systems Connection

Mobile enterprise applications connect with enterprise systems in a variety of different ways, including:

• ERP Systems
• CRM Platforms
• Identity Providers
• Legacy Data Sources
• Third-Party Applications

Architecture must also consider some very important factors:

• Latency when connecting various systems.
• Data consistency across multiple systems.
• Error-handling capabilities across multiple systems.
• Versioning mismatches between systems.
• Security boundaries between systems.

Loose-fitting between components of the enterprise architecture is critical to avoid cascading system failures.

Governance, Ownership, and Team Structure of the Enterprise Mobile Architecture

Enterprise mobile architecture will also be determined by the organization in which it resides.

Successful enterprise mobile architecture defines:

• Definite ownership of each service.
• Defined responsibilities for deployment of the service.
• Defined processes for establishing governance of the release of the service.
• Defined processes for managing the lifecycle of the API.
• Defined standards for documenting the API.

Without an established governance structure for APIS, even superior architecture will degrade over time.

Common Pitfalls of Enterprise Mobile Architecture

• Excessive Client Logic
• Mobile Applications as an Afterthought
• highly Coupled with the Legacy Functions of an Organization
• Ignoring the need to manage Version Changes for API’s
• Not Understanding Security Requirements
• Conception of the Application for Deployment Rather than Sustaining Longevity through Continuous Support

Most of the time when an enterprise fails, it is due to poor architectural decisions made in the early stages of development.

Evolving Enterprise Mobile Architecture through Time

Enterprise architecture will never remain stagnant.

Enterprise Architecture will continue to Change based on the following factors:

Usage Data
Changes within Organizations
New or Changed Compliance Requirements
Updates and/or Modifications of any of the underlying Technologies or Platforms
Expansion of the Business

Quality Architecture will anticipate and accommodate Change, thereby enabling evolution without excessive cost.

Final Remarks: Architecture is the Application underneath the Application

An Enterprise Mobile Application will Succeed or Fail Long Before the User Installs the Application.

The “Real” Product of an Enterprise Mobile application is the Architecture that LIVES UNDER the User interface. That is, the Operational Systems, Theney user or Adapters, the Architectural Decisions, and their Foundation Structures, to Allow the Enterprise Mobile Application to grow, Integrate and Adapt to Changing Environments OUS.

Finally, when Enterprise Mobile Application Architecture is highly defined and done Correctly, the following benefits result;

Teams Move Quickly and are able to Use Workload Efficiently.
Costs Stay Predictable.
Security Risks are Reduced.
User EXPERIENCE is INCREASED.
Applications can Survive Change, Evolution and the changing environment within Enterprise.

Survival is the Primary Measurement of Success in an Enterprise Environment.

Extended FAQs