3 ms·
Interesting. I'm guessing the extra layer may be needed for some manipulations of data at the application layer, but perhaps that is almost always avoidable?
by mixmastamyk 6y ago
Interesting. I'm guessing the extra layer may be needed for some manipulations of data at the application layer, but perhaps that is almost always avoidable?
Have you ever tried Hasura? I'm thinking of giving it a go in a future project.
- tylerhannan 6y agoIf/as you give it a go in the future...do let us know what is working and what could be better. We do, in fact, care. <disclaimer: I work at Hasura>
- musingsole 6y agoIt's only avoidable to the degree that your software architecture and company architecture allow you to make the more efficient decision to move the logic upstream. The cases where this pattern emerges are invariably because someone without insufficient access to the DB and its configuration bites the bullet and instead builds whatever they need to do it in the environment they have complete access to. I've similar problems lead to dead cycles in processor design where the impact is critical. These problems aren't software technology problems. They're people coordination problems.
- arcticfox 6y agoAs a Hasura user, I highly recommend it for OLTP workloads. And for the specific subject at hand (memory usage) it is fantastic. Its (in-database) serialization speed just completely runs circles around anything we could do before in Ruby.
- mixmastamyk 6y agoSounds correct to me. Although I've heard Ruby is slow, I suspect json serialization is done in C? At least it is in Python which I'm more familiar with. Simple cutting out the extra layers is where the big savings likely are.