Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
How about a library instead? The traditional way of reducing code duplication among separate software packages is to wrap the common bits in a library and use it where ever the functionality is ne...
#1: Initial revision
by
Iizuki
·
2025-03-11T08:54:28Z (22 days ago)
# How about a library instead? The traditional way of reducing code duplication among separate software packages is to wrap the common bits in a library and use it where ever the functionality is needed. Each microservice would still be talking directly to the external service, but most of the code handling it would not be duplicated. This assumes that your services are written in the same language. I would turn to extra services only after this approach starts falling short. E.g. perhaps because of complex data aggregation requirements.