3 ms·
An external chat service can be a pain in the ass just like a microservice. Depending if you want a lot of business rules integrated in that chat, you will have
by bicijay 3y ago
An external chat service can be a pain in the ass just like a microservice.
Depending if you want a lot of business rules integrated in that chat, you will have to keep data synced between your server and the chat's server. This can become a nightmare if you dont get it right.
- klabb3 3y ago> An external chat service can be a pain in the ass just like a microservice. Of course, because it’s just someone else’s microservice. Socially, it’s nice to have someone else take care of it. But technically, it’s more opaque than even your own microservices. > Depending if you want a lot of business rules integrated in that chat, you will have to keep data synced between your server and the chat's server. Right, because both the chat and your core service share users. So the boundary criteria for microservices, ie being standalone, is not there with chat, or many other types of services. From a technical perspective, these services would be better suited as libraries that require some integration work. However, that’s not conducive to usage based pricing, which is the snake within the microservice oil bottle.