2 ms·
One question I have with a project like this is: suppose I used it, and got traction. What is the story if I then realize that I need to migrate to a more tradi
by hyperpape 8y ago
One question I have with a project like this is: suppose I used it, and got traction. What is the story if I then realize that I need to migrate to a more traditional architecture?
- awake 8y agoTake the code they give you and change it?
- brett40324 8y agoThey dont give you code. You get an api with a postgres db on Amazon rds that you manage through forms.
- hyperpape 8y agoI think that's the ideal story: the system generates an intermediate representation that can be interpreted or compiled to a programming language. There are bindings to common languages/runtimes, and you can take your system and leave at any point. In practice, lock-in seems like a real issue.
- chris140957 8y agoHi, I've replied to this in another comment - BackendLab will soon allow you to export your app, as a Django project (the BackendLab API is built in django). That way, you can rapidly prototype using the interface, and then export and build it out further outside of the environment. The fact that the landing page doesn't yet mention this is a big miss - will try and get that updated soon