Rails is absolutely fantastic for projects below 10,000 lines with 1 or 2 contributors, especially if you want a classic forms-based UI. And you can get a huge amount done under those constraints in Rails. But as of couple of years ago, Rails came with a number of drawbacks: 1. There was no really viable system of static typing that a significant number of people were enthusiastic about. See... - Source: Hacker News / 29 days ago

Can you clarify what's the "tremendous value" you're getting out of the Django admin? At Heii On-Call https://heiioncall.com/ we are using Active Admin https://activeadmin.info/ for Ruby on Rails, which seems quite similar to the Django admin. In my experience, it's mostly useful as a fairly basic read-only view of what's in the database. In Rails, it's so easy to whip together a custom view that we tend to do... - Source: Hacker News / 7 months ago

For those who know [https://activeadmin.info/](https://activeadmin.info/) it uses a file format [https://github.com/activeadmin/arbre](https://github.com/activeadmin/arbre). Source: over 1 year ago

Very neat! My first thought was that this was a competitor to https://bullettrain.co/. Looking into it a bit more, it seems more aimed at building admin panels than whole apps. I guess it competes against tools like https://activeadmin.info/? - Source: Hacker News / almost 2 years ago

We briefly considered migrating to a full-grown Rails admin interface, such as ActiveAdmin, RailsAdmin, Administrate or Avo. We especially liked Avo which is built on a very modern stack similar to ours (Tailwind + Hotwire + ViewComponents). In the end, we didn’t go this route as we found some of the options a bit too restrictive (even though Avo is very flexible) and we did not feel like trying to amend it to our... - Source: dev.to / about 2 years ago

Another option could be ProxySQL, where you can cache queries on the ProxySQL server. Source: about 1 year ago

Also, if you're not using it yet, I can recommend looking at ProxySQL to do your read-write/read-only failover controls. Source: over 1 year ago

What are the recommendations here? I took a look into ProxySQL and it looks like since v2, it can do frontend and backend SSL connections. I have it locally working on a docker setup. Source: over 1 year ago

DB: Split you write-read operations. You may scale read as needed. Write operations can be slow if you have too many indices, so make sure to use only the ones you really need. Your DBMS may have some configuration to optimise, for example in MySQL if you do NOT need ACID compliance you can set innodb_flush_log_at_trx_commit = 2 to achieve better write speed. For MySQL you should also look into https://proxysql.com/. Source: over 1 year ago

A Layer-7 Database Load Balancer is optional here. An L7-DBLB can be used for various use cases (eg: ProxySQL). One or more database instances handle queries from the web server. A Client-side DB query/connection load balancing can also be used instead of an L7-DBLB according to the use case of the application. - Source: dev.to / almost 2 years ago