Re:Square’s terms of service forbid use of AGPL-licensed sof...
by Dayshine on Thursday June 06, 2019 @06:19AM
(#20113107)
Except AGPL doesn't have the linking exception from LGPL, so your entire application is covered.
A microservice doesn't get around it if it's tightly coupled. It would only be enough if your main application was not dependent on the AGPL microservice (e.g. you have another image processing microservice that provides perfect parity).
Re:Square’s terms of service forbid use of AGPL-licensed sof...
by jhauris on Thursday June 06, 2019 @09:51AM
(#20114530)
IANAL, but the source distribution requirement from network use only comes into play if the original AGPL work is modified. Section 13 of the AGPL seems to be the only part of the license that deals with remote network access, and it specifies modified versions. Everywhere else the discussion is around "convey", which in the definitions specifically excludes interaction over a network.
You only have to provide the source of derivative work, and only to users of your service.
So only the micro service using AGPL code.
If you use an AGPL database for example, you don't have to provide any source code unless you change the source code of the database. This idea was behind the business models of Rethink DB and Mongo DB.