Ask HN：我该用微服务架构还是单体架构？
1 分•作者: its_kritix•7 个月前
我正在使用一个基于 EPL 2.0 许可的开源项目构建一个 SaaS 应用，并希望加入我自己的 AI 功能。目前，我只计划将产品作为服务提供（不分发软件），但未来，我可能想创建一个独立的桌面 AI 应用。考虑到这些计划，我应该从一开始就将我的 AI 代码与 EPL 2.0 代码库分开，还是可以暂时将它们合并，以后需要时再分离？这两种方法的优缺点是什么，尤其是在许可、可维护性和未来灵活性方面？
我是一个独立开发者。
查看原文
I’m building a SaaS application using an open-source project licensed under EPL 2.0, and I want to include my own AI functionality. For now, I plan to only offer the product as a service (not distribute the software), but in the future, I might want to create a separate desktop AI app. Given these plans, should I keep my AI code separate from the EPL 2.0 codebase from the start, or can I combine them for now and separate them later if needed? What are the pros and cons of each approach, especially regarding licensing, maintainability, and future flexibility?
I am a solo developer.