Product Overview

Learn how our product can help you connect your applications to your users and devices to provide superior service.

Version: 1.0
Last Modified: 1/31/2020

What is MobiledgeX?

MobiledgeX is a developer-friendly, multi-tenant, on-demand set of edge services, enabling the deployment of applications, application components, and services that are much closer to the connected users and devices to provide superior service. For a developer, using MobiledgeX and the edge ecosystem ensures any edge service offered seamlessly integrates into existing methods of developing, while bypassing additional operational demands that burden most existing best practice cloud-based design workflows.

With MobiledgeX, you can:

  • Maintain views of edge systems, available resources, and topologies
  • Manage lifecycle management of applications
  • Allocate and manage storage and networking resources
  • Collect reporting information about your resources, and more.

Get started by creating an account.

Overview

The MobiledgeX Edge-Cloud infrastructure manages three cloudlet components that deploy MobiledgeX cloudlets as near the designated wireless network. Cloudlet components are installed as a platform cluster in virtual machines at the edge of the network and then managed by the MobiledgeX Edge Controller. Through the Edge Controller, applications can be on-boarded through a web console.

About the Edge Controller

MobileEdgeX Edge Controller is the custodian of all the available resource policies related to an application. The policies regarding where applications can be deployed and scaled are provided through the web interface of the application owner. An application owner may select from a preset location list to deploy their application. Once an edge compute instance is selected to deploy by the application owner, the MobiledgeX Edge Controller will distribute its services to that edge network instance. The Edge Controller becomes aware of the availability of an Edge location when the MobiledgeX cloudlet is deployed successfully at that location. Once the cloudlet is deployed, the Edge is made available to all applications for deployment.
The three components within the Edge-Cloud infrastructure include:

  • Distributed Machine Engine (DME): This is the first point of entry for all application contact from the client. In a given network, the DME knows all available cloudlets. When an application contacts the DME, based on the location (coordinates), the DME finds the most optimal back end for servicing the client.
  • Cloudlet Resource Manager (CRM): The CRM is responsible for managing all available resources in the system. It also ensures the liveliness of the application backends and monitors for their load. In cases where the edge can elastically scale the application backend using available API to the open stack endpoint, CRM will bring up new instances and remove existing instances based on resource utilization mechanisms.
  • Load Balancer (LB): All cluster bound traffic is load-balanced based on available resources on the application back end services. The load balancer acts as the network address translation (NAT) system, bridging the public and private networks.

The following diagram shows how MobiledgeX serves the distributed and application mobility workload.

MobiledgeX Architectural Diagram

Figure 1: MobiledgeX Architectural Diagram

Why use MobiledgeX as a Developer?

As a developer writing new edge applications, limitations either on the device or on-premise make scaling your resources and managing workloads extremely challenging. MobiledgeX relieves these challenges and allows for the optimal performance of services and applications.

If you answer yes to any of these questions below, MobiledgeX may solve the challenges that come with deploying applications allowing you to access and scale resources globally.

  • Does my application have real time-critical components?
  • Does by current client application experience limitations due to things like computing capability, memory, or storage availability?
  • Is my existing cloud application suffering from slow response times due to network delays?
  • Is the cost of data transfer between client and server costly?
  • Do I hesitate to send my data over the internet to a public cloud?
  • Do I have location-dependent data such as a model of the real-world environment and would appreciate the option to offload workloads?

For an in depth examination of the benefits of MobiledgeX, access our use cases here.

Where to go from here

  • If you're a Developer, get familiar with our Console
  • If you're an Operator, get familiar with our Console
  • Access our various Guides and Tutorials to learn how to leverage the MobiledgeX solutions