![]() ![]() Many of these companies have already been running for a number of years in relative obscurity compared with some of the better-known Web3 projects. The Web3 Index, provides an interesting snapshot of some of the companies and protocols building out this next iteration of decentralised platform building blocks. Where this cloud exists in a data centre controlled by the likes of Amazon, Microsoft or Google. Here, new opportunities for decentralisation start to emerge, which is an area that is lesser discussed at present, but will likely become commonplace as the Web3 industry evolves. These applications likely run within virtual machine containers on top of an orchestration platform such as Kubernetes in the cloud. It is here with the creation of the integration applications that centralisation starts to creep in, as we're now transitioning to an established, traditional stack for the execution of these applications. This is where front-end integration libraries such Hardhat or Truffle come in, or back-end libraries such as our very own Web3j library. They may also make use of decentralised storage technologies to store data off-chain in a decentralised manner.Īfter this point, the foundation stack ends and more traditional web technologies come into play, as an integration layer is required to bridge DApps to users or other services. Wallet technologies may also be used by users to interact with the DApps depending on their specific use case. The logic that runs these applications is embedded in smart contracts which define how the decentralised applications (DApps) themselves run. The execution layer sits on top of these layers providing the capabilities to actually run applications. ![]() This is underpinned by a consensus and data availability layer, which are enablers for the core ledger technology, rather than the specific application being built out. The distributed ledger or blockchain maintains the state of the application. There are additional components, for example, interoperability, layer 2s and naming protocols, but they won't be discussed here. ![]() These are typically making use of the following foundational building blocks, which I think of as the Web3 foundation stack: Decentralised Autonomous Organisations (DAOs).If we examine the core application themes as they stand in Web3, they are dominated by: Additionally, given decentralisation is a core theme of Web3, one can argue that a Web3 stack should be fully decentralised, which provides some interesting challenges to more traditional stacks. If we switch our attention to Web3, the notion of a stack is less well defined, which is a testament to how early we are still with respect to the evolution of this technology. PHP provides the web application framework encapsulating the business logic and presentation layersĪs the technology landscape has evolved so have the stacks, and in addition to these core web stacks, there are also stacks or applications for application performance monitoring (APM), business intelligence, load balancing, product analytics, machine learning, etc.MySQL provides the data persistence layer.Apache provides the webserver serving up the web pages.Linux is the underlying operating system (or Windows in the case of the lesser-known WAMP stack).The LAMP stack (Linux, Apache, MySQL, and PHP) is one of the best-known stacks, as it was a key building block adopted by Web2 companies such as Facebook, where each component of this stack has a clearly defined role. There are no strict rules as to what is defined as a stack, it's simply the sets of technologies you use to support various parts of your organisation. These groups of tools or frameworks, or stacks as you may, are crucial building blocks upon which technology platforms are built, using and deployed upon. The tech industry is bursting with stacks, be that the full-stack developer, LAMP, MEAN or Java stacks to name a few. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |