if anyone has been wondering: "SODEP (Simple Operation Data Exchange Protocol) is a binary protocol created and developed for Jolie". So far i didn't find any indication that Jolie supports grpc; I think that it would be very helpful if the developers decide to support grpc as well. https://docs.jolie-lang.org/v1.10.x/language-tools-and-stand...
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'll get around doing sooner or later though, since so many people use it, and we do care about interoperability. Contributions towards this would certainly be welcomed warmly.
if anyone has been wondering: "SODEP (Simple Operation Data Exchange Protocol) is a binary protocol created and developed for Jolie". So far i didn't find any indication that Jolie supports grpc; I think that it would be very helpful if the developers decide to support grpc as well. https://docs.jolie-lang.org/v1.10.x/language-tools-and-stand...
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'll get around doing sooner or later though, since so many people use it, and we do care about interoperability. Contributions towards this would certainly be welcomed warmly.
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.
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 some good questions in here.
I think the predominant question here is: why a language over, eg., a framework?
I'm very happy to see SOAP supported.... Well no, not happy, but... It's expected in many of the areas where I work. It's nice to see that I can easily create a SOAP webservice, without Java or .Net, but that there's anything wrong with those two languages.
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 (I don't at least), unless it's really necessary (interoperability with legacy web services, business requirements, etc.).
Super interesting! We're doing something similar with Encore [1], but instead of building a whole new language we let you program using Go. Looking forward to see where this goes :) [1] https://github.com/encoredev/encore
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 some good questions in here.
I think the predominant question here is: why a language over, eg., a framework?
Its cool that someone wrote this, but practically, this sounds like it encourages to microservice hell with many unnecessary services. A service should not be written to enforce separation of concerns. We have classes and functions for that.
In jolie, develoeprs program services instead of classes or functions. I think this is the main novelty introduced by jolie. Everything is a service, and you can postpone the decision on how to deploy an application. You can deploy it as a monolith (so your services will play the roles of classes, because they are internal) or independent services.