Full disclosure - also another Feathers maintainer here.<p>To add to @daffl&#x27;s comment...<p>Inevitably there is always some &quot;lock-in&quot; when you choose a technology and honestly we&#x27;re trolling Meteor a tiny bit, but I our aim with Feathers is to mitigate lock-in as much as possible by few design choices:<p>1) What daffl already said about small composable&#x2F;reusable modules<p>2) npm module support. You get to leverage all the awesome work others have done (without any additional overhead like porting modules or shimming them).<p>3) existing Express&#x2F;Connect middleware just works.<p>4) a very small codebase over top of another small modular codebase (express, socket.io). The theory being less code, means less to go wrong, which saves devs time writing code and debugging.<p>Ultimately, you do need to decide whether you want the Meteor sort of approach where it&#x27;s more of a kitchen sink that gives you all the tools you need but makes it hard to step outside the secure sandbox, or whether you want something that is a bit more flexible. Since, in my experience, all the projects I have worked on inevitably end up with something custom that the framework du jour doesn&#x27;t handle I prefer more flexibility and small composable modules.<p>We&#x27;ve tried hard to see if we can strike the balance between offering just enough without getting too much in the way. If you think we&#x27;re on the right track or not we&#x27;d love to hear your feedback.