5 ms·
How about: business logic is and remains private, but support libraries, boilerplate, etc is offered as discrete OSS repositories. This isn't too fancy - quite
by vemv 6y ago
How about: business logic is and remains private, but support libraries, boilerplate, etc is offered as discrete OSS repositories.
This isn't too fancy - quite commonly corps and startups alike offer some generic libraries. One can take that pattern to greater degrees.
This allows to scratch the itch of sharing something with the community, while still guaranteeing a livelihood.
Of course, it's mostly an incompatible approach for those favoring a strict monorepo- and microservice-based architecture.
- marvinblum 6y agoAgreed. If it's something that has no business value in itself and can be adopted by others (which might contribute in return), open-source it. There are also half-open/open-core models, see my comment below.
- mooreds 6y agoWe do this with a lot of our stuff at my current employer. It's a good compromise in my experience.
- zomglings 6y agogit submodules, despite their warts, do help incorporate a bunch of distinct code bases into a monorepo.
- mattbuilds 6y agoI have a similar plan with my current project [0] of interactive coding docs. The library to build the docs would be OSS. So anyone could build it and use it in their projects, But the business of hosting courses, payment, an advanced UI for building the docs would all be a SaaS. I think it's a nice balance that gives you the best of both worlds. [0] https://devbyexample.com https://devbyexample.com