Viewing profile — fmontesi

This question is in fact core to research in the paradigm. Let me first address how it works and then the expressivity question. A choreographic programming language features progr…

Indeed, one of the nicest aspects of Jolie is that you can (semi-)automatically extract the definition of the infrastructure that you need from your code. An example of a prelimina…

I was indeed talking about implementation models, in particular models of service-oriented systems. These are usually formulated in terms of services, DTOs, APIs, business logic, e…

In a nutshell: because we want to minimise code model distance. Other languages make you program in terms of functions, objects, etc., and make yourself model services by using the…

It's Jolie as in pretty, not as in Angelina. But I don't wanna stop you from making all these languages... (o:

IIRC, in industry, there is at least one big system with 50-ish microservices that includes electronic invoices. (See https://www.conf-micro.services/2019/papers/Microservices_20..…

Cool project, I'll check it out.

Thanks for the kind words, I'll share them with the rest of the team.

Yeah, we have SOAP because... SOAP (just because of interoperability). Our SOAP is quite palatable at least, because of reduced boilerplate. AFAIK Jolie devs don't typically use it…

PS: We support integration with Java, so you hack your way around this by using some Java code for grpc, but it doesn't feel "native" and require some boilerplate.

Jolie and SODEP predate grpc, so we don't have grpc just because we had no need for it (we already had a binary protocol with expressive interfaces). It's definitely something we'l…

Sure does. Jolie applications can be containerised like any other. See here for Docker and Kubernetes: https://docs.jolie-lang.org/v1.10.x/language-tools-and-stand... It's also bee…

Woah, so this happened. Maintainer here. I'll do my best to reply to all questions/doubts that get posted about an hour from now, since there is some valid feedback and there are s…

Here's also Github. It's resource-oriented instead of verb-oriented (like Telegraph), so we use Jor instead of Jo (both are provided by the same library). Jor["users/fmontesi/repos…

By the way, here's the Telegraph API documentation, for reference: https://telegra.ph/api What I wrote in my reply refers to that.

I can give you one by reusing a bit the Telegraph example I have in the Jo tutorial: http://fmontesi.github.io/2018/08/16/jo.html To create an account: Jo.createAccount( { shortNam…

A small library I made for fun. It's very early stage and I wanted to keep things simple, so it does not use any other established libraries (yet).

What we can do right now is having a microservice for input validation and call it when we need to validate something, both from the client and the server parts. In Jolie, adding c…

Leonardo is almost production ready, we usually just add some lines to tune the caching parameters as needed. This is the code for the Jolie website if you're curious about an exam…

It looks like another interesting difference may come from the workflow primitives (e.g., sequence, parallel, input choice) that Jolie comes with.

I would be very interested in seeing a comparison with gen_server, it looks interesting. Embedding in Jolie looks like a language primitive implementing something that resembles so…

Thanks, I get it now. If you use Jolie for implementing MVC, then every component is automatically a microservice (by construction from the language) and you can reuse them very ea…

Short answer: we usually don't use SOAP unless it is strictly necessary in your system. We have simpler and/or more efficient protocols. Long answer: We do not use SOAP when it is …

It may be the late hour here (CET), but I only kinda understood your question. What do you mean by "I can't replicate my model logic in my node services" ?