What are the details of deployment requirements (memory, storage, security, OAuth, etc.) of mimik edgeCloud backend on other platforms?

mimik hybrid edgeCloud platform back-end hosted on Amazon Web Services. mimik and Amazon formed partnership after Amazon did a technical DD on mimik’s architecture, scalability, security and reliability. Additionally; mimik offers a rich suite of application domain SaaS and edge serverless microservices for healthcare, fintech, gaming, AI, IoT, EdTech, etc. The application developers that are using mimik hybrid edge engine can host their own application domain back-ends on any public or private cloud of their choice.

Other than using APIs to get or create images and containers are there any examples showcasing how edgeEngine invokes APIs to use additional resources (e.g. GPU) on the backend?

• mimik edgeEngine and services such as FreeRTOS edgeSDK are downloadable software and therefore doesn’t provide low level hardware access. The edgeEngine provides information of OS, storage, memory, cpu, connectivity – IP address. The back-end is hosted in AWS so we don’t provide a view to availability of resource as cloud providers already do that.
• We have partners that provide machine vision as a service over GPU, CPU and FPGA.
• In regarding to invoking RESTful APIs on a custom backend, a serverless microservice can be developed and deployed to the edgeEngine in order to make calls to those RESTful APIs on a custom backend.

What are the details of deployment of mimik edgeCloud backend on the traditional cloud (e.g. Amazon Web Service) to support one million edge nodes

The back-end is highly scalable (as was validated with Amazon solution architects) and can support millions and millions of edge nodes and mainly b/c it was designed from ground up for supporting hybrid edge. The edge nodes are not polling back-end constantly. Everything runs in the most adhoc fashion. Nothing is pre-configured and communications amongst nodes are done via bootstrap model.

Elaborate on E2E technical architecture based hybrid edgeCloud technology

mimik provides Hybrid edgeCloud computing to enable any computing device outside the data center to support OS, CPU, memory, storage and connectivity on a cloud server. This helps developers unlock the next generation of apps for the hyper-connected world.

Such edge devices could include an Operator’s CPE. For example, OpenRAN with Lime microsystem, Wifi gateway, Smart TV, game council, smart phone, Robot as well as a sensor. edgeEngine is agnostic to OS, device, networks and public/private cloud. It's non-proprietary and works with existing standard development tools and languages.

mimik also provides ready to deploy application domain SaaS (cloud and/or edge) for a wide range of industry verticals. The mimik platform enables an edge-in versus a cloud-out approach to build applications faster and drastically reduce infrastructure cost, minimize latency and improve security and data privacy, and enable direct app-to-app communication via the standard RESTful API first and serverless microservice driven architecture. mimik’s platform is already used in multiple industry sectors including Fintech, signed up partners such Amazon Web Services and is part of 5G Open Innovation lab.

For more technical information on mimik technology, please view the following videos:

Siavash Alamouti keynote speech at the IEEE conference

Microservice edgeCloud Part 1

Microservice edgeCloud Part 2

mimik Microservices for mobile developers

Edge Computing Application Management with mimik CEO Fay Arjomandi

What other components or partnerships are required to have a complete solution for Hybrid edgeCloud platform using mimik?

mimik has taken signficant steps to ensure that it’s not introducing anything proprietary that forces application developers to use anything special technique or technology to develop their applications. mimik is takes the approach of RESTful API first for developing microservice architecture. Therefore, there is no need for any specific provider unless it’s driven by a business need and application specific use case.

How do device discovery, authentication and security protocols work under mimik?

mimik hybrid edgeCloud platform has been developed with a Security First approach. As a result, there are 6 levels of security built-in to the platform. These are:

1. Communication level: edgeEngine to edgeEngine authorization and authentication
2. Data level: AES -128bit encryption with 256bit key.
3. Protocol level: https & secure WebSocket
4. API level: All API(s) secured via OAuth 2.0 tokens for authorization and authentication.
5. Application level: OpenID connects.
6. Container level: Every microservice runs within its own container.

How does container / microservice instantiation occur in this architecture?

It depends on how the application is getting published. If it's a consumer application that's published on the Google or Apple app stores, a developer's application and serverless microservices are bundled as an APK and published on the given app store. edgeEngine is included wth the deployment.

An enterprise app goes through the enterprise application/solution deployment process that's used by the specific enterprise.

The serverless microservice can also get deployed dynamically dependign no the application use case, logic, and conditions. mimik also supplies a light container that is part of the edgeEngine. The light container is compatible with Docker and has the same API semantic as Docker. This means that an image that is hosted on a Docker repository in the cloud can be pushed to the given device that's running mimik edgeEngine or vice versa.

Also, an mimik image can be pushed to another edgeEngine based on application logic. As mentioned above, mimik provides the same API semantics as Docker. Thus, DevOps personnel can use other tools such as Kubernetes for orchestration and IBM Open Horizon for application management.

mimik's goal is to ensure that from the application developer point of view, everything remains the same and there are no proprietary tools or providers necessary with use mimik technology. mimik has taken care of all the underlying challenges and provides the necessary context via RESTful API(s) for application developers and DevOps to continue to focus on their business.

What's required to implement mimik Hybrid edgeCloud solution on a Windows / Linux platform (Edge device / hub)? Any specific requirements / dependencies?

There are no specific dependencies required to run mimik on Windows or Linux.

The following diagram illustrats the platforms that mimik supports:

[INSERT GRAPHIC]

What application could be supported for Proof of concept using mimik far edge solution?

• One application that you can use to see mimik underlying hybrid edge cloud platform in working is mimik access that can be downloaded from access.mimik.com
  • smart car/city with AirLin
  • content sharing with Lime microsystem
  • Gaming with 3BD
• mimik currently has customers in wellness, healthcare, fintech, smart mobility that either launched their applications using mimik platform or in the development phase. mimik is also actively in discussions with large industrial IoT for manufacturing automation, mining, department of Healthcare part of DoD and many others. The feedback is that mimik is the only solution that they have seen that can meet their full business requirements, and billion-dollar target revenue growth. mimik has a first mover advantage with a very unique value proposition that enables enterprises to unlock their business opportunities.

How to link mimik identity service with a potential partner and customer subscriber accounts? Example of OAuth API within mimik identity service?

mimik provides federated identity. We can jointly assess the potential partner/customer + mimik identity service interactions. All the Identity service API can be found on SwaggerHub, here published here.