If you are a Software Engineer interested in building out key components of an exciting, large-scale distributed platform in the cloud computing industry, please read on!
Are you interested in working with Java 8, Python, Apache Cassandra, Apache Spark, Redis, RabbitMQ, Apache Lucene cloud computing stacks, and other exciting and current technologies? Do you like the idea of building APIs other developers will leverage to build innovative web and mobile applications?
Join our team in Houston, TX as a Junior Backend Software Developer and have an impact on the cloud computing industry. This is only the beginning of what will surely be your most challenging and rewarding role to date; work with the latest technologies and push the barriers, all while helping build dynamic software that will have a lasting effect on the industry.
My best guess is that the java one is slow due to ebean (I've always seen huge performance improvements from switching to raw jdbc). The scala one I have no clue.
More likely because the version uses only as many threads as the cpu has cores. Whereas the servlet version for example has 128 thanks to the default resin configuration.
I think that the play-java one would likely benefit greatly from using raw jdbc rather than the ebean ORM. In fact my best guess is this is why the scala/java versions are so far apart. In past projects, scrapping ebean always led to large performance improvements in throughput, etc.
I have a general preference for Python + Flask/Django, postgres for SQL, and redis/mongo/cassandra for db/cache. With that said, I have no issue picking up new tech, as that's half the fun. You?
Lately I have been using Java/Scala + Play2 + MySQL and MongoDB/CouchDB. For some of my contract work I use the full JavaEE stack (including JSF, JSP, etc).
I have also used Python and Clojure quite a bit recently, and plenty of other frameworks and languages in the past.
Agree on the picking up of new techs being fun, probably why I have used so many different techs over the past few years.
