By Lex Pablo
We, at IT Cloud Solutions Australia, are at a stage post-realisation of the need for our ‘old’ database to be resurrected for main enterprise reportable data storage, and for running the business process layer, despite using an elastos sidechain (due to storage limitations on-chains). It appears that the Component Assembly Runtime, and CAR programming by us in C++, will provide our customers’ their way of connecting devices (phones, tablets, desktops) to a single enterprise database. My question is: will we be able to connect to a Middleware router on a node.js server in the Cloud (which interfaces to the Database itself, likewise in the Cloud) via Carrier from any registered device, and would the node.js server (router) require a copy of the Carrier system onboard? (thus requiring an Ubuntu OS). If so would you consider developing a version of Carrier for Alpine Linux for much reduced Disk Image Size in the node.js (router) Container?
Our plan as above assumes trusted Cloud Hardware for the Database and Backup System and for the Middleware Server. Is the Trusted Computing Enhancement relevant to Database and Middleware Security, directly on the hardware or in some other way (eg via Carrier)? (I understand the relevance of the Hardware Enhancement to Mining and ‘locking down’ blocks.)
Carrier at the moment does the most basic thing: Relays message from one node to another using decentralized carrier nodes with end-to-end encryption. So, some of the stuff carrier can be used for are apps such as messenger but it could also be used to transfer data from an IoT device(because carrier has a very small footprint, you can install it on top of anything including something like raspberry pi). These are just some of the use cases of carrier. There are many others.
As to the question you’re asking, carrier doesn’t necessarily need an Ubuntu OS to run. You can build it for various platforms such as Ubuntu, Mac OS, Windows, Raspberry Pi currently. Check out more at https://github.com/elastos/Elastos.NET.Carrier.Native.SDK. However, there are also SDKs available such as:
So, as you see, you can utilize node js SDK of carrier to write node applications that can then run on any platforms that can run a node program. Or, you can also interact with carrier from any mobile device since there are android and ios sdks also available. Or, you can also interact with carrier from a java program.
To clarify something, you do not need to install a native carrier node to use carrier functionalities because you can utilize various SDKs available in your existing app already. There are apps that already utilize carrier such as Hyper and it’s available for both android and ios i believe and there are more apps in development. The SDKs basically interact with some of the carrier bootstrap nodes(https://github.com/elastos/Elastos.NET.Carrier.Bootstrap) to connect to the carrier network that then lets you access carrier features from any apps you build.
As far as the Trusted Computing project, it’s more focused on strengthening the hardware itself when it comes to “Remote code executions”. So, in this way, in the future, anyone can utilize carrier node all over the world to execute random functions from any device in a completely secure way.
May I ask another question, please?
We need to know whether Carrier is able to connect to external websites and Rest API’s regardless of the underlying technology ‘powering’ the website or endpoints.