# Why choose Angus instead of vanilla Hyperledger Fabric ?

# Seamless integration with the existing systems

Integrating Hyperledger Fabric with existing legacy systems is difficult, especially when dealing with legacy backends. Angus makes it easier with plug&play gateway components such as Istio, Apisix, custom gateways..., allowing access to the DLT through generic interfaces like REST, message queues, or websockets.

# Easy operation with wide range of network deployments

Angus is based on Kubernetes, making it manageable through Kubernetes manifests, Helm charts, or its own angus CLI tool. There’s no need to understand complex shell scripts with thousands of lines or rely on special expertise, as existing IT staff can manage the entire Hyperledger Fabric infrastructure just like any other Kubernetes-native system, even if it is hosted on an arbitrary cloud or in your own server farms. GUI, command line, kubernetes manifest or REST API are all helping to seamlessly integrate into existing CI/CD tools.

# Establishing developer best practices:

Hyperledger Fabric does not provide clear guidelines for developing and maintaining chaincode, especially for production usage. Angus solves this by offering a full developer stack, including project skeletons, a development environment, and best practices for building, testing, and deploying applications — whether locally or in production. Angus provides also easy-to-use libraries to make the development and testing tasks much more efficient. The smart contract services can be accessed industry-standards - Sync/async, REST, message queues, websocket, etc.

# Focusing on common use cases

While Hyperledger Fabric is designed to solve a wide range of problems, enterprises often only need some specific features in a stable and reliable way. Angus provides out-of-the-box solutions for the most common applications but also offers enough flexibility for more complex requirements. It’s like the Unix philosophy: “do one thing, but do it well.”

# Vendor independency

Angus does not modify the core Hyperledger Fabric system. If you decide to move away from Angus, your Hyperledger Fabric system will continue to function without any issues. Angus helps manage the environment without taking full control of it. Furthermore, system administrators can use their own specialists for managing their infrastructure (Kubernetes) where they have their own rules/processes. By utilising industry standard approaches, Angus blockchain infrastructure would make integration into a seamless and effortless experience.

# Multi-network with on-premise support

Seamless integration between on-premise and cloud - you can effortlessly create or join other Angus or multiple distributed multi-cloud HLF networks on your preferred cloud or on-premise infrastructure.

# Governance support

In Hyperledger Fabric, managing information flow between organizations can be tricky, especially with new members joining channels,not even mentioning their certificate management…How do we store and make available the chaincode images, just for the ones with needed permissions? These are very important questions, and the answer is something like “do it in a way that it turns out well”. Okay, but how? On a floppy disk? Pendrive? Angus provides clear solutions to these governance challenges: Serving as a 'Corporate Secretary', it ensures that chaincode images and certificates are available only to the right people and always up-to-date.

# External database integration:

Bring your RDBMS/OODB/NoSQL DBs to create real-time queries or reports based on the blockchain data.

# Angus Center:

Remote management, automatic updates/fixes, automatic backup functionality