What I think is missing in this take is the separation of concerns and encapsulation of dependencies that services bring over libraries.
For example; a pdf transformation library may require a Linux machine for with custom PDF software, maybe even accelerated graphics hardware too. With a library I have to deal with all that, but a service can encapsulate that behind a HTTP interface.
Alternatively, with a pdf transformation library, you need to deal with those dependencies and hardware requirements yourself.
For example; a pdf transformation library may require a Linux machine for with custom PDF software, maybe even accelerated graphics hardware too. With a library I have to deal with all that, but a service can encapsulate that behind a HTTP interface.
Alternatively, with a pdf transformation library, you need to deal with those dependencies and hardware requirements yourself.