3 ms·
I would imagine being tied to Java at least by name (JavaSpace, Jini) is an impetus to push others away from it. That is why a "Soup of REST-ful services" is b
by rdtsc 12y ago
I would imagine being tied to Java at least by name (JavaSpace, Jini) is an impetus to push others away from it.
That is why a "Soup of REST-ful services" is becoming the lowest common denominator for distributed architectures (I think the buzzword I am supposed to use is "micro-services"). Because it is not tied to a language or platform.
Speaking of Sun's distributed systems, anyone remember JXTA? Looked really fun on paper, peer-to-peer overlay networks, send messages to anyone anywhere, works just "like pipes". Anyone ever used that? I learned about it school at one point during a project.
- patrickmay 12y agoREST is great for decoupling but as generally implemented it adds too much latency for some types of distributed computing. It also makes distributed transactions difficult to manage. Jimi addressed a lot of those problems in a technically interesting way. The protocol itself is language agnostic, but the implementation took advantage of Java's mobile code capabilities.
- rdtsc 12y ago> It also makes distributed transactions difficult to manage. Wonder if the typical REST-ful answer would be to make yet another service on top that manages distributed transactions and talks to a variety of other services. Sort of like APIs wrapping another APIs which wrap other APIs...