Who actually wants this? People want good libraries for doing this with the languages they already use, not to have to make compromises just so they can have a microservice. Notice that the front page gives lots of examples of the servicey parts of the code, but absolutely no examples of what the business logic looks like. In fact, even in the documentation, the example code is minimal and trivial.
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.
Wow. This looks really promising. I always found it a bit awkward that you have to bend the other languages to fit in the microservices model. I mean, yes, it's easy to do so in some of them but still there always seems to be a lot of boilerplate that you have to reiterate again and again. I think it was about time to have a language that takes care of the basics. Another one that I had in mind was ballerina (<a href="https://ballerina.io/" rel="nofollow">https://ballerina.io/</a>) but unsure how it actually fares so far.<p>Interested to hear production or even PoC stories on both of them.<p>Thanks for sharing.
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 :)<p>[1] <a href="https://github.com/encoredev/encore" rel="nofollow">https://github.com/encoredev/encore</a>
The JVM ecosystem is fairly amazing. I don't write much Java code anymore, but Clojure on the JVM is practical and modern, good for some of my projects.<p>I was looking at the Jolie (Java) source code and noticed a GNU license in some source code, but a top level Apache language - if I understand that correctly then that should be fixed.<p>Anyway, interesting project.
Slight tangent, but I much preferred the trend of language names being letters, gemstones, animals or coffee related, and something about programming languages names being commonly used woman names makes me uneasy. I don't know why, there's some sort of uncanny valley about it, some kind of scifi-esque AI-love cringe to it reminding me of the movie Her and the likes. I'm not dismissing the technical merits, and Julie sounds interesting, and I'm quite fond of Julia and Janet langs, but I've noticed this name trend and there's something interesting about this meta-social trend of using woman names for them.
The paradigm reminds me of the <i>message passing</i> paradigm in "early days" object oriented programming languages such as Smalltalk. I guess remote procedure calling (RPC) and message brokers (COM and friends) is the 90s or 2000s version of distributing these messages (network transparency). How does Jolie relate to these concepts?<p>I just wonder, when looking at enterprise Java, whether there are not mature libraries which allow for distributed and high level application writing without changing the whole software ecosystem.
The vision and model here seem excellent. Jolie as a language seems to have strong roots in academia and Europe. The one alarm is the lack of information on real world use, case studies and non-trivial adopters or users.<p>Anyone know of any large scale use of Jolie?
I'm very happy to see SOAP supported.... Well no, not happy, but... It's expected in many of the areas where I work.<p>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.
if anyone has been wondering: "SODEP (Simple Operation Data Exchange Protocol) is a binary protocol created and developed for Jolie".<p>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.<p><a href="https://docs.jolie-lang.org/v1.10.x/language-tools-and-standard-library/protocols/sodep.html" rel="nofollow">https://docs.jolie-lang.org/v1.10.x/language-tools-and-stand...</a>
Reflow [1] is a similar attempt at a slightly different domain: bioinformatics and ETL pipelines. Reflow exposes a data model and programming model that reclaims programmability in these systems, and, by leaning on these abstractions, gives the runtime much more leeway to do interesting things. It unties the hands of the implementer.<p>[1] <a href="https://github.com/grailbio/reflow" rel="nofollow">https://github.com/grailbio/reflow</a>
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.
Haven't looked at Jolie closely, but I am very well-versed in gRPC. Can someone give a quick comparison between the two or point me to a good resource that compares the advantages of Jolie over gRPC or vice-versa?