Dasync

Abstract

1. Introduction

D-ASYNC is a multifaceted and comprehensive solution for building service-oriented applications. It is based on the new Service-Oriented Programming Language paradigms, which provide an extendible framework for inter-service communication (HTTP, gRPC, message queues, event streams), a unique language-integrated stateful workflow engine, implementation of best microservice practices, a unified approach for distributed tracing, API generator and versioning capabilities, error-handler free clean code.

The mission of D-ASYNC is to give developers a superpower of zero-cost development of scalable, reliable, and secure microservices. The ability to use the language itself helps to focus on the core value of your application, making it easy to write, read, evolve, and maintain.

The following examples may look trivial and as for a single-process application, but D-ASYNC technology makes them run (without any modifications) in a resilient, persistent, scalable, and distributed manner. The new service-oriented syntax will be introduced with the CloudSharp project.

2. Objective

Every developer deserves the right of creating microservices without using any framework 🤍

This project demonstrates how C#, Serverless can be applied to a real-world Blockchain & Cloud Computing problem.

4. Technology Stack

5. System Requirements

General requirements for this technology stack — check the README for exact versions.

• .NET SDK / Visual Studio
• Git (to clone the repository)

6. Installation & Setup

git clone https://github.com/Dasync/Dasync.git
cd Dasync

1. Demo App
2. Walkthrough
3. Core Concepts

Full setup instructions are in the project README.

7. Future Enhancements

Suggested extensions you can add to make this your own project.

• Add a CI/CD pipeline with GitHub Actions
• Deploy to a public test network or cloud free tier
• Add monitoring and cost alerts

8. Viva / Review Questions

Common questions examiners ask for projects in this domain.

1. Why does this problem need a blockchain or cloud-native design?
2. Explain the smart contract / infrastructure components and how they interact.
3. How are gas costs or cloud costs kept under control?
4. How is the system secured (keys, IAM, access control)?
5. How would the solution scale to many more users?

9. Source Code & License

This project is developed by Dasync and published on GitHub under the Apache License 2.0. Please follow the license terms and credit the original author when you use or modify this code.