In our Rails application, we use the popular graphql Ruby gem to resolve GraphQL queries. When used naively, it essentially resolves queries as a depth-first tree traversal, which leads to the N+1 problem in GraphQL. - Source: dev.to / over 1 year ago

If you're comfortable on the react/client side with graphql, I'd highly recommend plugging in https://graphql-ruby.org/. Source: almost 2 years ago

The next step is to add the GraphQL gem to our Gemfile; you can visit its page, graphql-ruby, for more details; now, open your Gemfile and add this line:. - Source: dev.to / over 2 years ago

If you do go the API route though, strongly consider using GraphQL with the (graphql-ruby)[https://graphql-ruby.org/] gem. Source: over 2 years ago

GraphQL saves you time designing versioned REST endpoints. It self documents. Documentation isn't optional for serious web development so this is a huge win. The rails gems have gotten really good at picking up associations as well since I looked into a couple years ago. https://graphql-ruby.org. Source: over 2 years ago

I also read that Salt was using MessagePack to format their messages. MessagePack is a format like JSON, but more compact. - Source: dev.to / 8 months ago

So appreciate such a detailed reply, thanks. btw, why did you choose tinylib/msgp from 4 available go-impls? Source: over 1 year ago

If you find you're running the serial connection at maximum speed and it's still not fast enough, try switching to a more compact binary encoding that has both Serde and Arduino implementations, like MsgPack... Though I don't remember enough about its format off the top of my head to tell you the easiest way to put an unambiguous header on each packet/message to make the protocol self-synchronizing. Source: over 1 year ago

The information can be stored in a database or as files, serialized in a standard format and with a schema agreed with your Data Engineering team. Depending on your information and requirements, it can be as simple as CSV, XML or JSON, or Big Data formats such as Parquet, Avro, ORC, Arrow, or message serialization formats like Protocol Buffers, FlatBuffers, MessagePack, Thrift, or Cap'n Proto. - Source: dev.to / over 1 year ago

MessagePack Similar to JSONs, just more compact, although not as much as the ones above. Still, it's usefull to retain some readability in your messages. Source: over 1 year ago