Migrating from Node Redis to Ioredis: a slightly bumpy but faster road
This blog post tells the story of why and how we migrated from the Node Redis client library to Ioredis.
This blog post tells the story of why and how we migrated from the Node Redis client library to Ioredis.
In the previous article we discussed how to enable a server initiated encrypted connection to a Microsoft SQL Server. But what if we have a scenario where we do not want to incur the overhead of encryption for every application? In that scenario instead of configuring the server to force encryption we will instead need the client to initiate the encrypted connection.
Network encryption is a vital security step in hardening your application and guarding your data. Additionally, it is more often becoming a requirement by many organizations and laws (like HIPAA). In this article, we will discuss how to secure network communication between your application and the SQL Server database using an encrypted connection. We will demonstrate how encryption can be enabled and leveraged from SourcePro DB with no source code changes to your application.
A common problem that our customers have is event streaming spikey traffic to their clients. For example, imagine a server which needs to stream details on cryptocurrency trades. The quantity of trades happening each second is likely to fluctuate, sometimes nothing could happen, other times perhaps thousands. In order to ensure reliable communication, it’s important that rate limits are in place on how many messages are to be sent to subscribed clients.