请问HN：我应该使用微服务架构还是单体架构？
我正在构建一个基于开源项目的SaaS应用，该项目采用EPL 2.0许可证，我希望加入自己的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.