Differences

This shows you the differences between two versions of the page.

Link to this comparison view

irc:1461016800 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[09:22:32] *** ChanServ sets mode: +o temporalfox
 +
 +[10:44:22] <​luis_>​ Hi guys, we are working vertx for the backend of an app, and I have a few questions concerning Verticles vs Worker Verticles. I understand that Worker Verticles are meant to run sync code, but I would like to know if there is a real performance drawback using these types of Verticles. Basically, can I use Worker Verticles extensively or should I try to avoid them ?
 +
 +[10:55:53] <​cescoffier>​ Hi luis_ Worker verticle reduce your scalability as worker verticles are exuecuted in a worker thread pool
 +
 +[10:56:09] <​cescoffier>​ and they may be blocking, the thread utilization can be an issue
 +
 +[11:02:55] <​luis_>​ So if I can avoid them it's the way to go to ease scalability if I understand correctly ? Like they are meant to run legacy sync libraries but we should prefer opting for async libs when possible to use mostly Verticles ?
 +
 +[11:03:14] <​cescoffier>​ not sync, blocking. but yes
 +
 +[11:03:20] <​luis_>​ yeah blocking sorry
 +
 +[11:03:33] <​luis_>​ okay thanks =)
 +
 +[11:05:44] <​luis_>​ Also on an other hand, i saw you worked on the micro service toolkit for vertx 3.3, i was wondering if it was ready for production apps yet, or if it's to early ?
 +
 +[11:10:59] <​cescoffier>​ I guess it's almost ready :-)
 +
 +[11:11:30] <​cescoffier>​ there is some improvement around the documentation and I would like to have bridges for SRV record (DNS) and Consul
 +
 +[13:42:30] *** ChanServ sets mode: +o temporalfox
 +
 +[15:13:13] <amr> so using the mongo extended json api to insert a date ends up inserting a useless object {date: "​datestring"​} into my collection
 +
 +[15:13:28] <amr> looks like some sort of vertx wrapper
 +
 +[15:13:54] <amr> is that expected? it makes the data outside of its use with mongo pretty useless
 +
 +[21:04:56] <​dns_>​ hi! Is it possible to throw an exception from an async handler?
 +
 +[23:27:36] <​AlexLehm>​ dns_: the AsyncHandler is a Future subclass I think which means you can create a failure
 +
 +[23:28:29] <​AlexLehm>​ sorry, thats AsyncResult
 +
 +[23:30:43] <​AlexLehm>​ if your handler expects an AsyncResult<​T>​ you can use a failed future with throwable
 +
 +[23:32:29] <​dns_>​ AlexLehm: Do you mean Future.failedFuture("​Exception text"​)?​
 +
 +[23:32:38] <​AlexLehm>​ yes
 +
 +[23:34:23] <​AlexLehm>​ it doesn'​t really throw an exception, but the result code can check for !succeeded and get the exception
 +
 +[23:36:18] <​dns_>​ don't understand where sould I check a result of this future.. Could you please a link where I car read some examples.. may be.. I didn't find any examples except try {Future.get()} catch (bla ..) constructions(
 +
 +[23:36:51] <​dns_>​ I can create a gist example..
 +
 +[23:40:42] <​dns_>​ https://​gist.github.com/​zadoff/​638acaace85e2774a37b4f5502dcee40
 +
 +[23:40:51] <​AlexLehm>​ https://​github.com/​vert-x3/​vertx-mail-client/​blob/​master/​vertx-mail-client/​src/​test/​java/​io/​vertx/​ext/​mail/​SMTPTestBase.java#​L183
 +
 +[23:41:02] <​dns_>​ my question at line 35
 +
 +[23:42:44] <​AlexLehm>​ you cannot throw an exception in line 35 to the m1 method, since the code is not executed in that method, it is executed inside the class implementing the handler
 +
 +[23:43:21] <​AlexLehm>​ you have to use another handler to pass the exception I think
 +
 +[23:51:19] <​dns_>​ ok. Thank you!