4 ms·
> Why do you need to make the dependence on Redis a part of the public API? You don't do that with the service API, so why do you have to do it with the library
by DasIch 5y ago
> Why do you need to make the dependence on Redis a part of the public API? You don't do that with the service API, so why do you have to do it with the library API?
Where does the redis instance come from? How does the library get access to it?
These are problems the library author cannot solve and end up being problems for the user. Much like monitoring of that redis instance will also become a problem for the user.
- Tabular-Iceberg 5y ago> Where does the redis instance come from? Same place as it would if it was a microservice. Someone has to provision it, this is not automatic just because you use microservices. > How does the library get access to it? How does the microservice get access to it? A common way seems to be reading a host and port from an environment variable. Nothing is preventing a library from reading from an environment variable too. > Much like monitoring of that redis instance will also become a problem for the user. Again, this is something you still need someone to do for the microservice. None of these things are automatically solved by microservices. There are all kinds of automation tools for these things, but they work the same whether you use microservices or not.