3 ms·
> You write a library, then wrap a thin service interface around it. Distribute the lib as needed. Publish the service as needed. At $CURJOB, we did this but a
by mooreds 3y ago
> You write a library, then wrap a thin service interface around it. Distribute the lib as needed. Publish the service as needed.
At $CURJOB, we did this but at a higher level of abstraction (an authentication architectural component, rather than a library). I think this is what the author means when they say "writing a standalone server reached through a network protocol".
We see a lot of folks who like the flexibility of consuming functionality as a service or library, as they see fit. We've even had customers who said "we chose you because now we want you as a service, but later will want you as library" or vice versa.
Flexibility isn't free, though. Versioning, support, backwards compatibility (features and performance), even offering the service all become more complex.