|
Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ Set by moderator on 27 November 2017. |
|||
|
01:04
lizmat joined
02:58
ilbot3 joined
|
|||
| moderator | Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ | ||
|
10:17
lizmat joined
10:41
brrt joined
12:47
sena_kun joined
13:15
lizmat joined
15:36
Zoffix joined
|
|||
| Zoffix | So "micro services"... Is it just a buzzword? I'm looking for tools to build a site I estimate to be ~30K-60K LOC. Do I need "mega services" or will Cro do just fine? | 15:40 | |
| brrt | it is a buzzword for a service oriented architecture | 15:42 | |
| all sufficiently large programs devolve to a service-oriented architecture at some point | 15:43 | ||
| Zoffix | Don't see any template features in Cro. So it's not quite suitable to use as a "web framework", is it? | 15:44 | |
| jnthn | There's nothing stopping you brining your own template engine. | 15:45 | |
| *bringing | |||
| I don't think inventing yet another one will be much of a contribution. :-) | |||
| brrt | on the other hand, layering one on top with an ORM and distributing it as a 'web framework' is totally valid | 15:46 | |
| Zoffix | I think I'll try basing my Tardigrade web framework on Cro. Last time I tried making it, the amount of work needed to be done was quite overwhelming. But with routing and all the lower bits sorted, might be nice to try again. | ||
| Thanks \\o | 15:47 | ||
|
15:47
Zoffix left
|
|||
| jnthn | sub template($name, *%vars) { content 'text/html', call-your-engine($name, |%vars) } | 15:47 | |
| ah, he went :) | |||
|
16:04
brrt joined
16:28
brrt joined
22:58
Geth joined
|
|||
| japhb | "Tardigrade": Wow, that's a heck of a high reliability goal right there. | 23:10 | |
.oO( Can survive extended exposure to hard vaccuum and radiation, and get right back to serving requests as soon as it's near a network again ... ) |
23:12 | ||
| Geth | cro-http: 46eae7f51d | (Jonathan Worthington)++ | t/http-middleware.t Test Request/Response middleware roles with router These fall out of the two roles implementing Cro::Transform, so no extra work is needed to make them pass; still, it's good to have these cases explicitly covered. |
23:16 | |
| japhb | (explicit tests)++ | 23:17 | |
| jnthn | Too bad the "tardi" part might make one wonder if it's slow :P | 23:26 | |
| Hmm, I wonder if zef can take a github repo to install | 23:28 | ||
| Just realized that our Travis CI installs the Cro deps from CPAN | 23:29 | ||
| Meaning that cro-http tests can't take advantage of updates in cro-core HEAD, for example | 23:30 | ||
| ah, not a github repo, but the download URL of the ZIP github provides of master works | 23:32 | ||
| Geth | cro-tls: 027229fc4f | (Jonathan Worthington)++ | .travis.yml Test against Cro::Core HEAD |
23:34 | |
| jnthn | Let's see if that works out :) | ||
| Geth | cro-tls: 77093b444a | (Jonathan Worthington)++ | .travis.yml Correct mis-named Travis CI section |
23:47 | |
| jnthn | No, because I thinko'd the Travis section name | ||
| Nice news for those deploying on Kubernetes: cloudplatform.googleblog.com/2017/...ngine.html | 23:54 | ||
| Well, Kubernetes on GCE | |||
| (That's where cro.services runs, fwiw :)) | |||
| japhb | In Kubernetes? Cool! :-) | ||
| jnthn | Yeah | 23:55 | |
| And hosted on Google Cloud | |||
| Was pretty happy that I could re-use my prior Docker/Kubernetes experience | |||
| japhb | GKE FTW | ||
| Heh | |||
| jnthn | (First experience with the latter was at a place that really wanted to run the thing themselves. I'm glad to skip that bit of setup work.) | 23:56 | |
| japhb | I bet | ||
| Geth | cro-tls: 832b8b9125 | (Jonathan Worthington)++ | .travis.yml One install section is enough, d'oh |
23:59 | |