Redis VS Polly

The code uses the codehooks-js library to handle routing and middleware for the API, and the node-fetch library to make HTTP requests to the OpenAI API. The code also uses the built-in codehooks.io Key-Value store to cache the response from the OpenAI API for 60 seconds, in order to reduce the number of requests made to the OpenAI API (If you want to create your own Node.js Express backend, you just need to replace this cache with Redis for example).

Redis is an in-memory database and an open-source streaming engine with an IMDB data structure server that supports multiple data sets and data streams. This open-source platform has high throughputs and lower bandwidth due to its in-memory features that lead to faster processing of big data in data science applications.

Quirrel is a popular open-source webhook framework that makes it easy to add webhook support to your app. It makes uses of redis under the hood.

Redis

Redis is an in-memory data store that you can use as a database – or a cache in front of your regular database. The speed of Redis makes it ideal to cache database queries, complex computations, API calls, and session state.

I didn't finish college and I didn't see anything about Databases when I was there, so I don't have any theoretical background and on these 4 years coding at enterprise level my focus was totally in things like: Clean Code, SOLID, Design Patterns and other stuff code related and my only Database knowledge was about SQL/MySQL and Cache/Redis.

For the course I started to collect Open Source projects developed by corporations. There are a few where the product is open source such as Redis and Elastic. There are others where the company shares some of its code as open source such as Netflix, Facebook, or Booking.com.

The answer is yes. Introducing Redis, an open source database, in-memory, key-value data store and it is most-loved database by developers for five years running. Redis is commonly used as a primary database, cache, queue, and message broker. Redis is an open source (BSD licensed) that is used primarily as an application cache and quick response database and because the data is stored in memory rather than on a disk, Redis delivered unparalleled speed, reliability, and performance.

I'm not a C engineer, but I think I have an interesting recommendation to consider.

Since you are already familiar with other languages, you obviously don't need to know the basics of C. The basics are the same everywhere. Instead, you'd likely want to build that mindset on how to build good software with C.

I suggest you read other people's code and try to deep dive into the whys.

I heard Redis is a well-written software.

    git clone https://github.com/redis/redis.git

I don't know if it is the most elegant, or concise, or l33t, but I am in love with Polly https://github.com/App-vNext/Polly

One solution can be implementing the circuit breaker pattern for each microservice by using proven .NET libraries like Polly which is a very time-consuming and sometimes even challenging task.

it doesn't even throw when exception occurred, just a line of "Debug.Break", which means I can't use it with Polly

💡 Resiliency patterns - retry, cache, fallback, etc.: Very often, in distrusted systems world you need to ensure high availability by incorporating some resilience policies. Luckily, we have a built-in solution to build and define policies in .NET - Polly. There is out-of-the-box integration with IHttpClientFactory provided by Polly. This uses a convenience method, IHttpClientBuilder.AddTransientHttpErrorPolicy. It configures a policy to handle errors typical of HTTP calls: HttpRequestException, HTTP 5XX status codes (server errors), HTTP 408 status code (request timeout).

One of my favorite is Polly which provides a simple Circuit Breaker implementation plus other resiliency tools.

You do realize you are testing implementation details of a library which has its own public test suite? Code is available at https://github.com/App-vNext/Polly/tree/master/src/Polly.Specs/Retry/WaitAndRetryAsyncSpecs.cs

An SWE would likely guide the development and maintenance of any kind of SOA-based architecture, including writing and configuring the software to make it work. For example, a data scientist would not worry about using Polly for resiliency, or Consul for service discovery, and creating the libraries to use these systems.

Look into Polly resilience library. You can do much more with it, like automatic retries etc.

We need to bake in some level of resiliency by automatically retrying transient failures. This can easily be done by using something like Polly.