Jury.Online: From Monolith to Microservices
Jury.Online, a project implementing a concept of Responsible ICO, is continuously developing and improving in order to benefit our clients at most. After ICO Jury.Online project keeps working on business and an expanded service base.
Now the Jury.Online team is happy to announce that we have successfully launched the smart contract deployer through API. We are moving further away from one-framework code. Currently the deployer has already begun to operate with investment contracts, in the near future all contracts will be deployed through this service. Our deployer will allow the users to select the type of their roadmap, the number of mediators involved, the method of fee payment, and other. If the client/user needs another kind of smart contract, we will be able to deploy it in the shortest amount of time possible.
Jury.Online deployer is a Node.js service to greatly simplify the way our team and our platform interacts with our smart contracts — explains Juan Bernardo Tobar, Jury.Online top developer — It does so by exposing an API endpoint to be used programmatically (this is the way the platform connects to it), and by spinning up a point-and-click Graphical User Interface to be able to interact with our contracts in an intuitive way.
This accomplishes 4 things:
1) It separates the user platform from the blockchain. This is a strategic separation of services to offer a safer and more scalable overall infrastructure.
2) It exposes API endpoints: it allows our platform (and potentially other clients) to integrate our smart-contracts into their infrastructure.
3) It offers a GUI so that all of the members of our team (programmers and non-programmers) can interact with our contracts, work with them, find ways to improve them, deploy them via our service or via MetaMask (it connects to MetaMask browser), etc.
4) It facilitates the contract creation workflow. Now whenever we develop new contracts for our clients (as we are constantly innovating) and are ready to test them, we can just drop them in the deployer and automatically they will be available to use, deploy, and interact in the API and GUI.