I'm already lobbying for sequel AND roda internally for new projects. I particularly think that it's a much better fit for APIs than Rails, and for our particular use cases (a lot of legacy databases). Here's hoping I get my message across.
2016-04-25 0:35 GMT+02:00 Jeremy Evans <[email protected]>: > On Saturday, April 23, 2016 at 1:42:39 PM UTC+3, Tiago Cardoso wrote: >> >> Thx for the reply! I've managed to deploy a solution to our test servers >> with the option 1. So, the number of db connections will be N as in >> N=number of workers + 1 specific sequel db connection. This will be used by >> every worker, but just to build SQL, so I guess there won't be a lot (if >> any) of socket usage concurrency issues. It left me a bitter taste in my >> mouth, as I now have the feeling I'm using sequel as a much better Arel, >> and I've started calculating costs of migrating the app to sequel-rails, >> and actually use a proper tool for the whole stack. >> >> The migration path entails some concerns though. I assume you were going >> to say "roda" (I really like it, btw), but the "issue" regarding using >> these specialized non-rails tools is that you'll need developers who have >> some experience and can mitigate the learning curve. The advantage of rails >> is that any code school and "agile" course teaches it, not a lot of >> extra-training to do. I'm glad to pay the cost for sequel now, just not >> sure what are the long term costs of replacing the whole stack in terms of >> maintenance. I think roda and other frameworks need more adoption and >> visibility so that these costs are not as high, and right now, I don't see >> this happening. But hey, I could have said that from sequel last week and >> here I am talking about replacing active record. Here's to hoping that the >> situation changes and people appreciate these tools more. All the best and >> thanks for the work! >> > > I think you are very right. I was just being cheeky when I hinted at > switching from Rails to Roda. In general, in spite of the technical > advantages that Roda may offer, you definitely need to consider the network > effect benefits of using Rails. As you described, it's much easier to find > potential employees who are already knowledgeable in Rails. And currently, > many more libraries support Rails. I hope that these network effects > change over time, and I'm doing what I can to help them change, but they > are definitely something you have to consider when choosing whether to use > Rails or Roda (and similarly, ActiveRecord or Sequel). > > Thank you for your kind words, and I hope you are able to use Sequel > and/or Roda successfully in the future. > > Jeremy > > -- > You received this message because you are subscribed to a topic in the > Google Groups "sequel-talk" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sequel-talk/sM1S3KQQDj0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sequel-talk. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
