<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jolie &amp; LEMMA: Model-Driven Engineering and Programming Languages Meet on Microservices · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2104.02458/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2104.02458/feed.xml" rel="self" type="application/rss+xml" /><item><title>Jolie &amp; LEMMA: Model-Driven Engineering and Programming Languages Meet on Microservices — mentioned by fmontesi</title><link>https://news.ycombinator.com/item?id=27185143</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.02458:27185143</guid><pubDate>Mon, 17 May 2021 16:15:16 GMT</pubDate><description>&lt;p&gt;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, etc., hence the value brought by Jolie in giving a direct syntactic representation. The model of an implementation can change often, so it&amp;#x27;s important to have code that resembles it closely (for readability, editing, etc.). You&amp;#x27;re talking about the domain model, which I agree is more abstract and stable. It comes before making the implementation model. In the case of microservices, some concepts overlap and/or are…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.02458/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item></channel></rss>
