Skip to content

Release 1.5.0
Compare
Choose a tag to compare
@IrinaSouth IrinaSouth released this 10 Nov 08:18
· 457 commits to main since this release
featurehub-1.5.0
6f70d52
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This release includes architectural changes to improve FeatureHub deployability onto the cloud platforms and improve overall performance. For the full list of GitHub issues see here

For the overview of recent improvements, please see below:

Admin Console Web App

support for Keycloak - this adds support for Keycloak - OAuth2 identity provider. Docs

Backend

Breaking changes

The breaking change only affects all-separate setups and only Edge configuration. Make sure you update
dacha.url configuration according to this docs

Non-breaking changes

super-light weight deployment option - A new bundled deployment, party-server-ish - which contains the Admin web app, the Admin backend (MR), and edge-rest together as one bundle. It is an ideal deployment for a low-use website and is covered in our installation docs. As it includes edge-rest it can’t be used for streaming updates, but if you have a mobile app or web app or you are OK with GET/polling updates, this is a low-cost deployment option.

light-weight edge services - edge splits into Streaming+REST and REST - so there are now two docker images, the existing one, edge which talks to dacha, and edge-rest which talks directly to the database. This makes edge-rest suitable for deploying into a container runtime platform like KNative, Google Cloud Run or Azure Container Instances.

reduced data egress costs - Edge now supports etag and this is now folding into the following SDKs: Javascript Node and Javascript Client. This significantly decreases data egress costs when features have not changed, and increases the ability to use a CDN in front of Edge if you wish.

deployment configuration - all configuration properties are now available in the same case as environment variables, previously they were required to be upper case and have . replaced with _. We did this for environments like Cloud Run and ECS.

enhanced, more performant, rest based cache - Dacha, our caching layer moves to being a REST server from being a NATS server with a monitoring only REST api. It is intended to be an internal only facing REST service but while it consumes the NATS updates from MR, it exposes its caching for REST purposes and enhances the data it returns (to include portfolio, application, etc).

database read replicas - All systems that talk to databases now support a read replica using the db-replica. or DB-REPLICA_ prefix for specifying configuration. This means an increased number of database connections, and balancing your read only queries into the read replicas. Docs installation docs

massive performance increases for GET requests - Significantly enhanced read operations for GET requests on Edge - we have really focused on performance here and managed to get a 9x performance improvement for the dacha based platform. The edge-rest based platform depends on availability of your database connections so will be a bit slower.

Assets 2
Loading