Tech Holding | NFTs and digital currency combined

NFTs and digital currency combined

When it comes to uniting cryptocurrency and non-fungible tokens, both markets of which are quite unstable, the development team has to face regular changes to the current goal of the development.

Overview

When it comes to uniting cryptocurrency and non-fungible tokens, both markets of which are quite unstable, the development team has to face regular changes to the current goal of the development. In this fast-paced environment, adapting to client's requests and changes fast is a crucial requirement that underlying infrastructure has to support.

Achieve a goal

To achieve a goal of varying objectives, we decided to build a multi-purpose underlying infrastructure using AWS, that could accommodate the company dynamics. In conjunction with GitHub actions we were able to launch services and shut them down as we needed them. In addition, AWS provided us the ability to scale up and down quickly with minimal cost.

The approach of business goals

This approach enabled the team to stay focused on business goals without time and monetary expenses invested into infrastructure that can potentially become unnecessary. With our infrastructure properly set and provisioned, the team had no longer spent time on dev ops and could simply add needed functionality to the suitable place within the infrastructure. With AWS, it also provides the ability to expand in the future easily if we want to use one of the multitudes of services it provides.

Approach

Architecture

The central piece of the application is determined to be a front-end client written in React. The application would be built with GitHub actions and hosted on AWS S3. The wallet agents and NFT canisters would connect directly to the front-end via 3rd party identity providers, and run on Dfinity network. The client involves support from the server, written in Node.js and deployed to AWS Fargate. This container service gives a lot of flexibility in terms of rapidly expanding to accommodate incoming requests, shrink down to save costs, and swiftly host desired features.

Adaptivity

The infrastructure setup allowed us to have a modular approach to design and development. The front-end client components are regarded as modules that could be turned on or off, modified, and have assets swapped through Contentful integration. This feature allowed applications to get the application to a production-ready state with minimum effort. The same modularity can be seen on the server: USD, ETH and BTC transaction operations are modularised as individual tasks and can easily be enabled/disabled, modified and deployed with practically no impact on the production state. During private sale the server also featured whitelisting for a limited time which worked flawlessly for the load within the AWS Fargate engine.

Conclusion

Crypto market is a new and desirable technological domain. When combined with NFT, the direction of development might easily change, and our approach fits well for the environment. Combined with GitHub actions and Contentful, AWS allows us to modify the application fast and easy, making the deployments seamless and the service constantly available for the end user.