Wow that is so true, thanks for sharing
boriscy
OvermindDL1
Back when I had to run it before replacing it with something better it has major security issues at the start until those ‘features’ were individually turned off, it was significantly slower than what it was replaced with, and it had a nasty habit of using classes that were loaded from being replaced when the .war(?) updated, forcing a reload. Just to start…
Uh, why? In the past I’ve used MySQL, Sqlite, Oracle, Riak, and at least a dozen other things. Maybe you are talking about Ecto and not Elixir. Ecto is not Elixir, and Ecto is not the only SQL library out for Elixir/Erlang. 
1
svsdehh
we replaced tomcat with with anothter container a short time ago and went back to tomcat as our monitoring showed, that the app was slower. After going bacl to tomcat the response time decreased again.
I do not know whether this still exists, as we are always starting new instances when deploying.
But only maybe. 
Actually we do not use Ecto at all and are working directly with the DB driver. In our case mongodb.
We started with the mongodb driver and realized later that it does not support replica sets. that means that driver was simply not production ready and merely a proof of concept. thats you do experience with java.
and lately we made a proof of concept application where we had to access a teradata DB. for this project we did not even consider elixir as the language of choice. does there exists a teradata driver for elixir?
1
peerreynders
Technically I would classify Ecto as a Data Mapper (or more accurately as part of one**) - and the issue is that a significant segment of the developer population has come to expect the presence of data mapping - rather than having to get their hands dirty (… suffering a loss in their productivity) writing their own low level persistent storage logic.
**As far as I can tell Ecto is only capable of defining it’s own structs (types) via the schema mechanism - I haven’t come across functionality that would let it deal with structs (types) that have been defined outside of Ecto (yet). So I imagine that would necessitate defining your domain types to contain an opaque portion for the Ecto struct and declaring the data inside the domain type off-limits for direct access (probably a good idea anyway). However I would imagine that the functionality for the domain module could still get messy especially if it has to deal with nested types that are represented by separate Ecto structs.
2
Ankhers
Just in case you were not aware, I finished replica set support recently.
There is actually an erlang mongodb driver that has supported replica sets since May 2011.
If you cannot find what you consider to be a production quality library in Elixir, make sure you look for one in Erlang.
2
svsdehh
thanks for letting me know.
Yes, we already knew that and we tried to migrate the db driver and ran into some problems. I already created an issue at github about it.
thats surely a good tip. but when we started with elixir we did not want to dive directly into another language we were not familier with. but nevertheless that a good tip.
0
OvermindDL1
It is really still the same language, just different syntaxes. Never be afraid to look at erlang libraries, it has quite a lot.
0
svsdehh
[quote=“Ankhers, post:44, topic:6501”]
Just in case you were not aware, I finished replica set support recently.[/quote]
and… btw… thank you very much for finishing this! ww were looking forward for getting this feature!
1
Ankhers
heh, didn’t realize that was you. Hopefully I should be fixing it shortly. I’m pretty sure I know what the issue is.
No problem. Just glad it is useful to people.
2
