It is a protocol and network designed to create a content-addressable, peer-to-peer method of storing and sharing hypermedia in a distributed file system. | It is a lightweight, highly modular, reactive, type safe Java and Android library for working with Smart Contracts and integrating with clients (nodes) on the Ethereum network. This allows you to work with the Ethereum blockchain, without the additional overhead of having to write your own integration code for the platform. |
IPFS is a peer-to-peer distributed file system that seeks to connect all computing devices with the same system of files. In some ways, IPFS is similar to the World Wide Web, but IPFS could be seen as a single BitTorrent swarm, exchanging objects within one Git repository. In other words, IPFS provides a high-throughput, content-addressed block storage model, with content-addressed hyperlinks.[11] This forms a generalized Merkle directed acyclic graph (DAG). IPFS combines a distributed hash table, an incentivized block exchange, and a self-certifying namespace. IPFS has no single point of failure, and nodes do not need to trust each other not to tamper with data in transit. | Complete implementation of Ethereum's JSON-RPC client API over HTTP and IPC;
Ethereum wallet support;
Auto-generation of Java smart contract wrappers to create, deploy, transact with and call smart contracts from native Java code (Solidity and Truffle definition formats supported);
Reactive-functional API for working with filters;
Ethereum Name Service (ENS) support;
Support for Parity's Personal, and Geth's Personal client APIs;
Support for Infura, so you don't have to run an Ethereum client yourself |
Statistics | |
Stacks 208 | Stacks 43 |
Followers 181 | Followers 39 |
Votes 0 | Votes 0 |
Integrations | |
| No integrations available | |

It tailors your application for GraalVM and HotSpot. Amazingly fast boot time, incredibly low RSS memory (not just heap size!) offering near instant scale up and high density memory utilization in container orchestration platforms like Kubernetes. We use a technique we call compile time boot.

It is a first class persistence framework with support for custom SQL, stored procedures and advanced mappings. It eliminates almost all of the JDBC code and manual setting of parameters and retrieval of results. It can use simple XML or Annotations for configuration and map primitives, Map interfaces and Java POJOs (Plain Old Java Objects) to database records.

A decentralized platform for applications that run exactly as programmed without any chance of fraud, censorship or third-party interference.

It is a collaborative effort created to advance blockchain technology by identifying and addressing important features and currently missing requirements. It leverages container technology to host smart contracts called “chaincode” that comprise the application logic of the system.

The Guava project contains several of Google's core libraries that we rely on in our Java-based projects: collections, caching, primitives support, concurrency libraries, common annotations, string processing, I/O, and so forth.

It is a modern server-side Java template engine for both web and standalone environments. It is aimed at creating elegant web code while adding powerful features and retaining prototyping abilities.

It is used for building component-based user interfaces for web applications and was formalized as a standard through the Java Community

It is a software which can be used to achieve Byzantine fault tolerance (BFT) in any distributed computing platforms. It consists of two chief technical components: a blockchain consensus engine and a generic application interface.

It is a platform that helps users to establish a certain private Blockchains that can be used by the organizations for financial transactions.

It is used to monitor Java or Java EE application servers in QA and production environments. It is not a tool to simulate requests from users, it is a tool to measure and calculate statistics on real operation of an application depending on the usage of the application by users. It is mainly based on statistics of requests and on evolution charts.