Charlie, doing DB calls in Spray has nothing special or different from what you would do with plain Akka, Play or any other toolkit. Certainly, there is a preference for using async and non-blocking drivers, but that is not a requisite. What really matters in case you are doing blocking calls to a database (using JDBC, for example) is that you set up a dedicated dispatcher (like a thread-pool) to be used by those blocking tasks. That way the blocking part of your app wont eat all the threads and starve the rest of the components.
With regards to managing and monitoring, of course the first option would be the Typesafe Console [1], built by the same people working in Akka/Play. Also, there is a project we are working on right now [2], focused in Akka and Spray (Play support might arrive in the future).. we are in the process of tidying up the basic set of features and writing docs for our first public release which will get out very soon. Last, but not least, there is the monitor [3] tool for Akka created by the Cake Solutions team (correct me if I'm wrong!) which is also open source. Hope this info helps! best regards!. [1] http://typesafe.com/platform/runtime/console [2] http://kamon.io [3] https://github.com/eigengo/monitor On Tue, Jan 21, 2014 at 11:27 AM, Pascal Voitot Dev < [email protected]> wrote: > I'm not an expert in Spray in prod (more Play experience) but there are a > few articles you can find on Google on how to monitor an Akka app... > You've got Typesafe Console naturally which is specifically dedicated to > this and a few tools to add on top of Akka! > > Other people might have far better advices than mine on this point! > > Pascal > > On Tue, Jan 21, 2014 at 3:18 PM, charlie robert <[email protected]>wrote: > >> Oh, yes, could you also mention about management and monitoring with >> Spray, as well? >> >> - charlie >> >> On Jan 21, 2014, at 7:15 AM, charlie robert <[email protected]> wrote: >> >> Hi pascal, >> >> This sounds promising. However, our kafka consumers need to do some DB >> calls, but in a high volume sort of way. Could you say a few words about >> database interactions in Spray? >> >> thanks, >> charlie >> >> On Jan 21, 2014, at 1:03 AM, Pascal Voitot Dev < >> [email protected]> wrote: >> >> Yes clearly you can get rid of servlet stuff and go to frameworks like >> Play or Spray! >> Spray is more low-level and is better if you want pure REST (more is >> possible too but it's more "manual" than Play). It's also 100% actor based >> with akka.io >> Play is full-stack and can help if you want more than just REST (it >> provides everything to build web apps)... It uses Netty for now as network >> layer (spray will be integrated later) and doesn't rely on actors for >> network part (you can use actors in your application) >> >> Both are performant. >> In terms of connection pooling, you won't manage it anymore as with >> servlets as you'll enter the world of stateless/non-blocking/async where >> you have a very few threads switching very quickly instead of a big pool >> like servlets. >> So you have to stop thinking about sticky sessions, stateful sessions and >> blocking code etc... >> But it brings real benefits, you'll see ;) >> >> pascal >> >> >> On Tue, Jan 21, 2014 at 3:28 AM, Robert Withers <[email protected]>wrote: >> >>> Which Akka-based REST servers include support for connection pooling, >>> without a Servlet 3.0 container? It may be fun to ditch Tomcat. We had an >>> issue where multiple jars were stomping on each other and the WAR was >>> exiting with no information. 2 weeks of team investigation finally >>> identified the setting that needed to change…turn off string-encodings in >>> wily. If Play or Spray can match performance, connection pooling and log >>> configuration, it would be an option for a proof-of-concept. Any >>> recommendations? >>> >>> Thanks, >>> - charlie >>> >>> >> >> >> >> >> >> >> >> - robert >> >> >> >> >> >> >> >> >> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user >> --- >> You received this message because you are subscribed to the Google Groups >> "Akka User List" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: http://akka.io/faq/ > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/groups/opt_out. > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
