snowflake VS Ruby on Rails

If you're not distributed, use an incrementing integer.

If you're distributed, look into vector clocks[1] or snowflake[2]

[1] https://en.wikipedia.org/wiki/Vector_clock

[2] https://github.com/twitter-archive/snowflake/tree/snowflake-...

MongoDB ObjectId Time, Clocks, and the Ordering of Events in a Distributed System Snowflake

There are so many of them in big data, e.g. Kafka, Spark, Flink, Delta, Snowplow, Finagle, Deequ, CMAK, OpenWhisk, Snowflake, TheHive, TVM-VTA, etc.

Twitter built Snowflake https://github.com/twitter-archive/snowflake/tree/snowflake-2010

that being said, I have seen people acting weird about the whole thing, I don't care if you're mad at HYBE or BIGHIT for not telling him, what I care about are these people acting as if Jimin cannot deal with this or handle it himself. why they are THEY asking an explanation to be given to them? this is none of your business, he's a grown man and he can handle it himself. it's funny because even if he was to talk to someone about this, we will never know and that will be him dealing with his issue. they sit on twitter.com and try to play BTS manager and think they how BTS should be managed and HYBE needs to do things their way. they have managers for a reason and we are not the ones, I can't even believe this whole thing blew up so much.

Coincidentally, the default Puma configuration in the most recent Rails release is similar to what's shown here (thanks to Nate Matykiewicz for the tip).

Starting in Rails 7.1 we have "normalizes" as a declaration to make in our models. It provides the same functionality, but in a different manner.

MR to update Spanish translation

It is also known to build secure applications, and the active community does well at finding solutions to the newest vulnerabilities. The Ruby and Ruby on Rails documentation are great resources for delving into this ecosystem, but if you prefer a guided path, The Odin Project open-source community would be an excellent start.

Hey Andrew! So good to see you here. I agree with everything you said 100%. I am honestly split, because I was the first one recommending engineers if_not_exists, but now I am torn, because this can lead to very weird issues in production, esp. for ActiveRecord apps, and maintaining a "invalid index reaper job" doesn't sound like a good long term solution.

I did suggest some proposals to Rails here and would love to propose a PR based on a solution that makes the most sense too

https://github.com/rails/rails/issues/52583

I think the hardest part is deciding which gems to use. It's not uncommon to end up with over 50 gems in your Gemfile.

For example, built-in capabilities for authentication are limited: https://github.com/rails/rails/issues/50446

So then do you go with has_secure_password/etc., Devise, rodauth, authentication-zero, or something else? These are big decisions that then might affect other things like authorization, OAuth, PassKey, etc.

And that's authentication & authorization which are a relatively well-understood and maintained area, but other areas might have totally unmaintained gems that might have issues with recent versions of Rails, or native module compilation issues with more recent versions of operating systems, etc.

A lot of Rails guidance on blog posts and StackOverflow might be outdated.

This problem is not unique to Rails. I still think Rails is great and relatively vibrant. Nevertheless, I suggest being very wary of Rails guides, blog posts, and StackOverflow answers that are more than 1 year old and doing a careful study and inventory of gems before deciding to use them and reviewing their relative recent usage and activity.

In Rails 7.2, this option changes from query_constraints to foreign_keys. Besides the parameter name change, some interesting discussions are underway about plans to repurpose the original query_constraints name by freeing it up.

The guides are inside the Rails repository - https://github.com/rails/rails/tree/main/guides.