Recently, we implemented some Java-based services using JDBC. And some time ago, I refactored some legacy PHP programs that used "csession" for communication between systems to use PDO with ODBC.
This raised a question for me about how license management is done in this scenario. Is a license used per pool? Or per connection? How is this management done?
In some cases, it's necessary to manipulate data from one namespace to another. For example, a routine in the "N1" namespace needs data from the "N2" namespace. In legacy systems (using only globals), it's common to make the global universal, but what about persistent classes? Is this type of globalization also possible?
In my previous article, I structured network communications in these 3 possible layers, and covered the last
Client <---> Transport
Server <---> Transport
Client <---> Server
In fact, you have the most control over the last one. The IRIS side as a server is yours and under your full control. Up to now, the Transport layer was assumed to be as passive as a bare wire.
Chasing errors or misbehavior in the network can be quite a challenge. Differently to a local application on the DB server, you always have at least 3 players:
A client to place a request
some kind of transport layer
and a server to provide a reply.
This results in a minimum of 3 possible communication layers
As a developer who uses Cache as DB for a couple of projects, I'm using REST API's every time, knowing how to consume a resource from REST API, in my opinion, it's crucial to know how to consume external REST Api's using %Net.HttpRequest because it enables integration with modern web applications and services, and it's a crucial skill for a backend developer who loves and uses Cache as a DB.
By update