You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I watched the Strange Loop talk and played around with the Outboard API over the weekend. I am very impressed with the work being done here. Being able to treat the database as a persistent data-structure just as any other built-in Clojure data-structure brings a lot of benefits to the table. Even more compelling than the performance benefits are, for me at least, the advances in semantics. It makes writing production applications more simple. By eliminating the need for database interfaces, ORMs, query DSLs, ad-hoc synchronization mechanisms, all still commonplace in real-world Clojure, a lot of complexity is effectively reduced. In other words, there is great value here.
I would like to test this library in real-world applications as soon as possible, and help others do the same. I am planning to write a component for it for inclusion in the system library.
I have two immediate concerns that you might be able to address.
Make all operations safe. API calls will be made in threads, typical of web applications, so race conditions should be excluded. Here, for example.
Package the library and make it accessible on Clojars so that we can incorporate it in our build tools.
Again, I view the work done here as a fundamental piece completing the programming model promised by Clojure with regards to the functional paradigm. I see many reasons to prefer this project over Datomic, especially for small production applications. The API is brilliant and joyful to use. I would be thrilled to witness its usage spread out.
Thank you so much indeed.
The text was updated successfully, but these errors were encountered:
The API is actually safe, within the construct of the JVM. The mechanism that Outboard uses to ensure that only 1 database is made by each name is valuable since it ensures that users can't accidentally clobber their data by running the side-effectful database creation function. This is the same sort of mechanism Datomic uses: an idempotent connect function.
I would certainly be excited to package the library, but I'm not sure that I'll have time over the next couple of weeks. I'll begin to gather together some of the issues that need to be resolved before release, though.
I watched the Strange Loop talk and played around with the Outboard API over the weekend. I am very impressed with the work being done here. Being able to treat the database as a persistent data-structure just as any other built-in Clojure data-structure brings a lot of benefits to the table. Even more compelling than the performance benefits are, for me at least, the advances in semantics. It makes writing production applications more simple. By eliminating the need for database interfaces, ORMs, query DSLs, ad-hoc synchronization mechanisms, all still commonplace in real-world Clojure, a lot of complexity is effectively reduced. In other words, there is great value here.
I would like to test this library in real-world applications as soon as possible, and help others do the same. I am planning to write a component for it for inclusion in the system library.
I have two immediate concerns that you might be able to address.
Again, I view the work done here as a fundamental piece completing the programming model promised by Clojure with regards to the functional paradigm. I see many reasons to prefer this project over Datomic, especially for small production applications. The API is brilliant and joyful to use. I would be thrilled to witness its usage spread out.
Thank you so much indeed.
The text was updated successfully, but these errors were encountered: