Replies: 1 comment 1 reply
-
Thanks @arysom, I appreciate your thoughts. Interestingly, I haven't found much use for creating custom entities. Mostly I find that everything I've thought would be a good fit have actually done an amazing job just being unpublished nodes. In the project I am currently working on, we discussed it again. The architect was leaning towards using a custom table but in the end, we all felt like having the data in nodes had too many benefits e.g. using views, direct editing etc. I'll ponder more on the other issues. I have more info on caching for sure and did play a fair amount with Varnish and Fastly. Not sure my notes are that useful tho. |
Beta Was this translation helpful? Give feedback.
-
creating custom Entities , there's a lot in Drupal docs about it, but maybe you could share some of your experiences. There are certain situations, where someone asks me to create a webapp with relations, data types and all that and it occurs that I can't mimic standard mysql model, I have to be creative. There's timestamp field, but it doesnt fit and so on. And the relationship, I'm using entity reference field, but in the end I produce a relation that looks like it's reverted - not standard one to many, but rather many in one. Or maybe that's my point of view.
creating apis with drupal, json vs rest, currently I'm into Next-Drupal - fine project, was afraid to use jsonapi, but now a little less afraid.
performance stuff - lot of area to cover, from time to time I come back to this book, and it's still valid. Lot of ideas from it are precious.
Beta Was this translation helpful? Give feedback.
All reactions