From 9a7cd8ce662595091f99d51be988aaad101959c8 Mon Sep 17 00:00:00 2001 From: asim Date: Mon, 8 Jul 2024 18:52:06 +0100 Subject: [PATCH] update readme --- README.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 3882135442..45648257cf 100644 --- a/README.md +++ b/README.md @@ -19,8 +19,8 @@ Go Micro abstracts away the details of distributed systems. Here are the main fe - **Dynamic Config** - Load and hot reload dynamic config from anywhere. The config interface provides a way to load application level config from any source such as env vars, file, etcd. You can merge the sources and even define fallbacks. -- **Data Storage** - A simple data store interface to read, write and delete records. It includes support for memory, file and - CockroachDB by default. State and persistence becomes a core requirement beyond prototyping and Micro looks to build that into the framework. +- **Data Storage** - A simple data store interface to read, write and delete records. It includes support for many storage backends +in the plugins repo. State and persistence becomes a core requirement beyond prototyping and Micro looks to build that into the framework. - **Service Discovery** - Automatic service registration and name resolution. Service discovery is at the core of micro service development. When service A needs to speak to service B it needs the location of that service. The default discovery mechanism is @@ -40,12 +40,6 @@ Go Micro abstracts away the details of distributed systems. Here are the main fe - **Async Messaging** - PubSub is built in as a first class citizen for asynchronous communication and event driven architectures. Event notifications are a core pattern in micro service development. The default messaging system is a HTTP event message broker. -- **Event Streaming** - PubSub is great for async notifications but for more advanced use cases event streaming is preferred. Offering - persistent storage, consuming from offsets and acking. Go Micro includes support for NATS Jetstream and Redis streams. - -- **Synchronization** - Distributed systems are often built in an eventually consistent manner. Support for distributed locking and - leadership are built in as a Sync interface. When using an eventually consistent database or scheduling use the Sync interface. - - **Pluggable Interfaces** - Go Micro makes use of Go interfaces for each distributed system abstraction. Because of this these interfaces are pluggable and allows Go Micro to be runtime agnostic. You can plugin any underlying technology.