Tag Info

New answers tagged

1

Packages on the JVM have a very important job – to provide a globally unique namespace for all your classes. It doesn't matter whether you write your code with Scala or Java or Clojure; in the end all get compiled to .class files or JAR archives. Note that Scala is not the Anti-Java, instead interoperability with Java was a primary design goal. So the ...


2

Scala package best practices are generally the same as Java conventions, according to the Style Guide. // wrong! package coolness // right! package com.novell.coolness // right, for package object com.novell.coolness package com.novell /** * Provides classes related to coolness */ package object coolness { }


1

You should not use a container, but use a containerless framework such as Play instead. Regarding your points: Single Point Of Failure: This is independent of deploying in a container or not. I you just deploy one instance of your app and it crashes, it's down. For high availability you'd use multiple running instances and load balance between ...


2

I'm not sure how easy this would be to implement in Scala, but here's how I'd look to structure it in Haskell: To begin I'm going to review a couple of the monads which Haskell and F# provide -- You're probably familiar with them, but I'll review them just to set the stage. In Haskell there is the IO monad which is used for doing IO operations (e.g. web ...



Top 50 recent answers are included