Layotto (L8): To be the next layer of OSI layer 7
[](https://github.com/mosn/layotto/actions/workflows/quickstart-checker.yml)
[](https://github.com/mosn/layotto/actions/workflows/layotto-ci.yml)
[](https://godoc.org/mosn.io/layotto)
[](https://goreportcard.com/report/mosn.io/layotto)
[](https://codecov.io/gh/mosn/layotto)
[](http://isitmaintained.com/project/mosn/layotto "Average time to resolve an issue")
Layotto(/leΙͺΛΙtΙΚ/) is an application runtime developed using Golang, which provides various distributed capabilities for applications, such as state management, configuration management, and event pub/sub capabilities to simplify application development.
Layotto is built on the open source data plane MOSN .In addition to providing distributed building blocks, Layotto can also serve as the data plane of Service Mesh and has the ability to control traffic.
Motivation
Layotto aims to combine Multi-Runtime with Service Mesh into one sidecar. No matter which product you are using as the Service Mesh data plane (e.g. MOSN,Envoy or any other product), you can always attach Layotto to it and add Multi-Runtime capabilities without adding new sidecars.
For example, by adding Runtime capabilities to MOSN, a Layotto process can both serve as the data plane of istio and provide various Runtime APIs (such as Configuration API, Pub/Sub API, etc.)
In addition, we were surprised to find that a sidecar can do much more than that. We are trying to make Layotto even the runtime container of FaaS (Function as a service) with the magic power of WebAssembly .
Features
- Service Communication
- Service Governance.Such as traffic hijacking and observation, service rate limiting, etc
- As the data plane of istio
- Configuration management
- State management
- Event publish and subscribe
- Health check, query runtime metadata
- FaaS model based on WASM and Runtime
Project Architecture
As shown in the architecture diagram below, Layotto uses the open source MOSN as the base to provide network layer management capabilities while providing distributed capabilities. The business logic can directly interact with Layotto through a lightweight SDK without paying attention to the specific back-end infrastructure.
Layotto provides SDKs in various languages. The sdk interacts with Layotto through grpc. Application developers only need to specify their own infrastructure type through the configuration file configure file provided by Layotto. No coding changes are required, which greatly improves the portability of the program.
Quickstarts
Get started with Layotto
You can try the quickstart demos below to get started with Layotto. In addition, you can experience the online laboratory
API
| API | status | quick start | desc |
|---|---|---|---|
| State | β | demo | Write/Query the data of the Key/Value model |
| Pub/Sub | β | demo | Publish/Subscribe message through various Message Queue |
| Service Invoke | β | demo | Call Service through MOSN (another istio data plane) |
| Config | β | demo | Write/Query/Subscribe the config through various Config Center |
| Lock | β | demo | Distributed lock API |
| Sequencer | β | demo | Generate distributed unique and incremental ID |
| File | β | TODO | File API implementation |
| Binding | β | TODO | Transparent data transmission API |
Service Mesh
| feature | status | quick start | desc |
|---|---|---|---|
| istio | β | demo | As the data plane of istio |
Extendability
| feature | status | quick start | desc |
|---|---|---|---|
| API plugin | β | demo | You can add your own API ! |
Actuator
| feature | status | quick start | desc |
|---|---|---|---|
| Health Check | β | demo | Query health state of app and components in Layotto |
| Metadata Query | β | demo | Query metadata in Layotto/app |
Traffic Control
| feature | status | quick start | desc |
|---|---|---|---|
| TCP Copy | β | demo | Dump the tcp traffic received by Layotto into local file system |
| Flow Control | β | demo | limit access to the APIs provided by Layotto |
Write your bussiness logic using WASM
| feature | status | quick start | desc |
|---|---|---|---|
| Go (TinyGo) | β | demo | Compile Code written by TinyGo to *.wasm and run in Layotto |
| Rust | β | demo | Compile Code written by Rust to *.wasm and run in Layotto |
| AssemblyScript | β | demo | Compile Code written by AssemblyScript to *.wasm and run in Layotto |
As a FaaS(Serverless) runtime (Layotto + WebAssembly + k8s)
| feature | status | quick start | desc |
|---|---|---|---|
| Go (TinyGo) | β | demo | Compile Code written by TinyGo to *.wasm and run in Layotto And Scheduled by k8s. |
| Rust | β | demo | Compile Code written by Rust to *.wasm and run in Layotto And Scheduled by k8s. |
| AssemblyScript | β | demo | Compile Code written by AssemblyScript to *.wasm and run in Layotto And Scheduled by k8s. |
Presentations
- Layotto - A new chapter of Service Mesh and Application Runtime
- WebAssembly + Application Runtime = A New Era of FaaS?
Landscapes
Layotto enriches the CNCF CLOUD NATIVE Landscape.
Community
Contact Us
| Platform | Link |
|---|---|
| π¬ DingTalk (preferred) | Search the group number: 31912621 or scan the QR code below  |
How to contribute
Where to start? Check "Community tasks" list!
As a programming enthusiast , have you ever felt that you want to participate in the development of an open source project, but don't know where to start? In order to help everyone better participate in open source projects, our community will regularly publish community tasks to help everyone learn by doing!
Contributors
Thank y'all!
Design Documents
Pubsub API and Compability with Dapr Component
FAQ
Difference with dapr?
dapr is an excellent Runtime product, but it lacks the ability of Service Mesh, which is necessary for the Runtime product used in production environment, so we hope to combine Runtime with Service Mesh into one sidecar to meet more complex production requirements.