5 ms·
I don't agree with this. I'm just a small developer working for a medium-sized company, but I'm a python guy and I love RDBs and REST/JSON. Sometimes it's easi
by nodja 10y ago
I don't agree with this. I'm just a small developer working for a medium-sized company, but I'm a python guy and I love RDBs and REST/JSON.
Sometimes it's easier for me to alter the JSON payload a certain way in the frontend, then the python backend handles it and saves it to the DB.
The RDB helps not to stray too far into crazy-land, while python and JSON gives you the flexibility to prototype and experiment.
- ci5er 10y agoIn the absence of a good reason not to use Python (and there are many case where one should not), I use it quite a bit myself. And usually (absent good reason) I use it with PostresQL. SQLAlchemy is a wonderful thing. Granted, I am neither a database nor ORM savant, but I find that it makes explicit almost as easy as implicit - but with more safety! I haven't seen that elsewhere, but I haven't looked very hard either. I have heard claims that Groovy/Hibernate do this just as well as well, but it isn't clear to me that this is completely true.
- _asummers 10y agoYou should check out what the Elixir folks are doing with Ecto. I'm a huge fan so far!
- ci5er 10y agoThanks for the pointer. I'm already using BEAM in a project, so that wouldn't be a bridge too far for that one...
- _asummers 10y agoConceptually, everything is a Schema and then you generate Changesets for DB operations like insert, update, etc. and apply various validations and transformations as a chain of function calls on the input map. No such thing as a model anymore. It fits really nicely with a data > functions mindset.
- ci5er 10y ago> It fits really nicely with a data > functions mindset. That will probably confuse my procedural mind, much like declarative "stuff" often does! :-)