From 7e7fae095312dcd6317ac04b12939c46e8bb17eb Mon Sep 17 00:00:00 2001 From: ainsley Date: Wed, 13 Nov 2019 16:31:05 -0600 Subject: [PATCH 1/3] folder fix --- SUMMARY.md | 3 ++- whats_new.md | 23 +++++++++++++++++++++++ whats_new_20.md | 2 +- 3 files changed, 26 insertions(+), 2 deletions(-) create mode 100644 whats_new.md diff --git a/SUMMARY.md b/SUMMARY.md index 36c44b2..dd8a0d7 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -1,7 +1,8 @@ # Table of contents * [Introduction](README.md) -* [What's New in 2.0](whats_new_20.md) +* [What's New!]() +* [NATS 2.0](whats_new_20.md) * [FAQ](faq.md) ## NATS Concepts diff --git a/whats_new.md b/whats_new.md new file mode 100644 index 0000000..3811e9b --- /dev/null +++ b/whats_new.md @@ -0,0 +1,23 @@ +# What's New in NATS + +The NATS.io team is always working to bring you features to improve your NATS experience. Below you will find feature summaries for new implementations to NATS. Check back often for release highlights and updates. + +## Server release v2.1.0 +### Service Latency Tracking + +As services and service mesh functionality has become prominent, we have been looking at ways to make running scalable services on NATS.io a great experience. One area we have been looking at is observability. With publish/subscribe systems, everything is inherently observable, however we realized it was not as simple as it could be. We wanted the ability to transparently add service latency tracking to any given service with no changes to the application. We also realized that global systems, such as those NATS.io can support, needed something more than a single metric. The solution was to allow any sampling rate to be attached to an exported service, with a delivery subject for all collected metrics. We collect metrics that show the requestor’s view of latency, the responder’s view of latency and the NATS subsystem itself, even when requestor and responder are in different parts of the world and connected to different servers in a NATS supercluster. +* Release notes [2.1.0](https://github.com/nats-io/nats-server/releases/tag/v2.1.0) +* Full list of Changes [2.0.4...2.1.0](https://github.com/nats-io/nats-server/compare/v2.0.4...v2.1.0) + +## Server release v2.0.4 + +### Response Only Permissions + +For services, the authorization for responding to requests usually included wildcards for _INBOX.> and possibly $GR.> with a supercluster for sending responses. What we really wanted was the ability to allow a service responder to only respond to the reply subject it was sent. + +### Response Types + +Exported Services were originally tied to a single response. We added the type for the service response and now support singletons (default), streams and chunked. Stream responses represent multiple response messages, chunked represents a single response that may have to be broken up into multiple messages. + +* Release notes [2.0.4](https://github.com/nats-io/nats-server/releases/tag/v2.0.4) +* Full list of Changes [2.0.2...2.0.4](https://github.com/nats-io/nats-server/compare/v2.0.2...v2.0.4) diff --git a/whats_new_20.md b/whats_new_20.md index ee9a3a0..022663a 100644 --- a/whats_new_20.md +++ b/whats_new_20.md @@ -1,4 +1,4 @@ -# What's New in 2.0 +# NATS 2.0 NATS 2.0 is the largest feature release since the original code base for the server was released. NATS 2.0 was created to allow a new way of thinking about NATS as a shared utility, solving problems at scale through distributed security, multi-tenancy, larger networks, and secure sharing of data. From 721dbe389648c077aa4d0dca0ffbf8f68ca0b261 Mon Sep 17 00:00:00 2001 From: ainsley Date: Mon, 6 Jan 2020 10:30:34 -0600 Subject: [PATCH 2/3] added queue permissions --- whats_new.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/whats_new.md b/whats_new.md index 3811e9b..72f90d6 100644 --- a/whats_new.md +++ b/whats_new.md @@ -2,6 +2,12 @@ The NATS.io team is always working to bring you features to improve your NATS experience. Below you will find feature summaries for new implementations to NATS. Check back often for release highlights and updates. +## Server release v2.1.2 +### Queue Permissions + +Queue Permissions allow you to express authorization for queue groups. As queue groups are integral to implementing horizontally scalable microservices, control of who is allowed to join a specific queue group is important to the overall security model. Original PR - +More information on Queue Permissions can be found in the [Developing with NATS](developing-with-nats/receiving/queues#queue-permissions) section. + ## Server release v2.1.0 ### Service Latency Tracking From 99baefddddb79ea641aafece02b8d727c800857c Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Mon, 6 Jan 2020 10:33:48 -0600 Subject: [PATCH 3/3] Update whats_new.md --- whats_new.md | 1 + 1 file changed, 1 insertion(+) diff --git a/whats_new.md b/whats_new.md index 72f90d6..305516e 100644 --- a/whats_new.md +++ b/whats_new.md @@ -6,6 +6,7 @@ The NATS.io team is always working to bring you features to improve your NATS ex ### Queue Permissions Queue Permissions allow you to express authorization for queue groups. As queue groups are integral to implementing horizontally scalable microservices, control of who is allowed to join a specific queue group is important to the overall security model. Original PR - + More information on Queue Permissions can be found in the [Developing with NATS](developing-with-nats/receiving/queues#queue-permissions) section. ## Server release v2.1.0