SONM Updates and Specifies its Roadmap for Q4 2017 — Q2 2018
Reasoning behind the roadmap update
One of the SONM goals has always been to build a high-quality production-grade platform that competes with the industry’s major players. Therefore, we’re applying enterprise-level software development processes and techniques, which require that we conduct the following procedures:
- Gather software requirements specification, namely the use cases — what the user can do with the system
- Design elaboration
- Deployment and maintenance
These processes are based on software requirements, which are, in turn, based on stakeholders’ needs and expectations. Any project defined at the high level undergoes the process of requirements specification, whereby the product vision and features are optimised and prioritised. It is important to understand that programming is not the only and final part of the development process. Code must be tested (Quality Assurance), and the system must be carefully deployed.
The SONM roadmap outlines the project plans of the company and can be adjusted to reflect changes in the process. The previously published roadmap in the SONM white paper overviewed the development processes and covered plainly the product. The main traits of the prior version and the reasons of its being rewritten are the following:
- It was not use-case (or function-)oriented. The description provided was focused on technical details, rather than specifying what the user will be able to do with the system and which use cases or user-aware features will be available upon each release.
- It was not measured against a continuous delivery and deployment cycle that is sustainable for cryptocurrency-based projects.
- It stated promises for specific but rather low-level features.
In order to transform this roadmap into a working plan, the team had to clarify requirements and address the abovementioned roadmap traits. This revealed a strong and reasonable need to define when a generally working product would be delivered for a public test.
According to the first version of the roadmap, the release of the working product relates to v1.0 “DOMIN”: — “The very first commercial version of this platform for public usage.”
The team decided to define the details of what the first working product will contain and when it will be delivered.
The first generally working product was defined as a marketplace due to be delivered in February 2018 on testnet. The roadmap has successfully been updated to reflect this.
Roadmap update details
We developed a component structure of the project which includes the following layers:
This layer provides the ability to buy and sell computation resources. The item, which can be bought and sold, is a computer resource slot (CPU, RAM, disk, network, and optionally GPU) that is rented over a period of time. It has characteristics, a time frame, and a price. Hardware owners may install SONM and rent out their machines. Consumers may install SONM, look for resources on the market, buy them, and then launch their own tasks on their purchased resources. This approach requires the customer or his or her application to take care of scheduling, scaling, and load-balancing. This will benefit some applications.
- First building block of the future platform (SONM PaaS will be built on top of it)
- Debut of SONM computing open market, where all transactions are in crypto currencies
- Analog to Google Compute, the foundation of the Google Cloud infrastructure
- Allows the user to select the right amount of computing resources to fit the required parameters for a particular use case
- Provides an infrastructure that can execute any Linux-based application safely inside the Docker container
- Already allows users to scale out applications, but requires the user to program the scalability logic
- Needs to manage its own data; logical volumes can be created on the host
This layer is the same for hardware providers, but introduces fresh functionality for computing customers. PaaS allows a customer to define an application and let SONM automagically schedule and scale it. This also provides a base for fog services.
These layers will be implemented sequentially because PaaS requires IaaS in order to operate.
The first layer to be implemented is IaaS, which will be delivered gradually through the following major releases:
(1) “MVP-testnet” (former v0.3 “ARCH”) — December 2017 — January 2018.
The first major release will contain the minimum viable product (MVP) and will be launched on the Ethereum test network (RINKEBY).
This release will contain core market functions and will provide operational IaaS product, which can be used by an applications with their own scaling logic and data management (application level).
- Face recognition in video streams using ML
- Video rendering (e.g., using Blender renderer)
- Web hosting (at the first stage with public data: for example, content delivery networks, wiki-like websites)
- Scientific calculations
- Backend for managed data storage services (object storage, NAS); encryption and replication performed by client nodes
- SONM nodes can be used for large-scale deployment of new projects (including crypto projects): for example, content delivery systems, decentralised web hosting platforms, or even new crypto currencies wishing to gain scale quickly.
The MVP, as the first working marketplace, must be tested on the Ethereum test network in order to ensure security.
- Marketplace — buy and sell resources, launch tasks on purchased resources
- Payout app
(2) “Rating system pack” (former v0.4 “POWER”) — February — March 2018
- Rating system (this function will be possibly included in “MVP-testnet”)
- Profiles and the network
- Storj integration
(3) “Arbitrage and various features pack” (former v0.5 “VIRT”) — May — June 2018
- Arbitrage and deal- and dispute-solving system (former court app)
- Fees payout
(4) “Core IaaS-livenet” (former v1.0 “DOMIN”) — July — August 2018.
This major release will contain all MVP functionality and additional features launched on the Ethereum live network.
(5) Next major releases — PaaS development, IaaS maintenance/development, and “Future” — summer 2018 and later. The exact release plan from Release (5) onwards is to be estimated and planned.
Wallet app releases
Wallet is a GUI application that makes the SONM platform user friendly and is a simple and modern tool that uses common SONM features. Wallet’s functionality is loosely coupled with the SONM core (Iaas/PaaS), so Wallet has a special development team and release cycle.
However, Wallet features will become available to the public around the same time as the SONM core “MVP-testnet” release.
(1) “Wallet prototype” — around December 2017.
The first major version will implement the MVP GUI, enabling user experience for SONM-core MVP features implemented in MVP-testnet (see above).
- SNM token and Ether works — check balance, set allowance, make transfers, view operations history.
- Voting for token holders.
(2) “Market GUI” — February — March 2018
- Functionality with the SONM network — create profile, etc.
- Browser for sites (hubs)
- Marketplace GUI — sell or buy resources.
(3) “DAO GUI” — May — June 2018.
- DAO tab (including voting) — allows the user to take part in the DAO.
(4) “Wallet IaaS-livenet” (former 1.1 “THRON”) — July — August 2018.
This major release will provide user experience for SONM-core IaaS-livenet functions (see above).
(5) Next major releases.
- Application management tab — define (create) applications, launch applications, watch logs, etc.
- App store.