|
|
Subscribe / Log in / New account

Microservices 101: The good, the bad and the ugly (ZDNet)

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 12, 2015 11:53 UTC (Sun) by torquay (guest, #92428)
Parent article: Microservices 101: The good, the bad and the ugly (ZDNet)

    "... doesn't suddenly mean your badly architected ball of mud is suddenly really well architected and no longer a ball of mud."
Pot, kettle, black. RHEL is a mud ball in the first instance, with no clear separation between apps and the OS (among other crimes).


to post comments

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 12, 2015 13:11 UTC (Sun) by pizza (subscriber, #46) [Link] (1 responses)

The problem with all of this "Service" and "abstracting" handwaving is that folks forget that at some point the turtles have to stand on something in order to actually interface to the real world.

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 13, 2015 14:54 UTC (Mon) by SEJeff (guest, #51588) [Link]

You're not fooling me, it's turtles all the way down!

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 12, 2015 14:25 UTC (Sun) by HelloWorld (guest, #56129) [Link] (1 responses)

> no clear separation between apps and the OS
Yeah, just like pretty much every other Linux distro. Except that Red Hat actually pays somebody to work on fixing this, i. e. the whole systemd/Gnome application containers thing.

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 13, 2015 5:55 UTC (Mon) by salimma (subscriber, #34460) [Link]

Not to mention the interesting work on "rings" being done as part of the Fedora Server working group, which should trickle down into the next version of RHEL

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 13, 2015 11:45 UTC (Mon) by nim-nim (subscriber, #34454) [Link]

Actually Red Hat is thriving precisely because RHEL is sane and sturdy enough to resist the garbage app people sell to enterprises.

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 13, 2015 14:55 UTC (Mon) by SEJeff (guest, #51588) [Link] (7 responses)

Have you even seen RHEL Atomic? For Atomic, your comment simply could not be further from the truth.

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 13, 2015 16:38 UTC (Mon) by drag (guest, #31333) [Link]

I've been using it and so far it's pretty awesome.

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 14, 2015 7:24 UTC (Tue) by torquay (guest, #92428) [Link] (5 responses)

erm? Atomic is for running Docker containers. I'm referring to user-facing stuff like evince, firefox, libreoffice, gimp, etc. They spew their files all over the file system, mixing in with OS level components. On top of that, a security hole in firefox has the potential to expose all of the user's data.

Or is there already a containerized version of firefox?

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 14, 2015 14:43 UTC (Tue) by drag (guest, #31333) [Link] (1 responses)

> Or is there already a containerized version of firefox?

There is, but it's not going to be easily usable in a manner that is suitable for a workstation or desktop. People are working on sandboxing/containerizing desktop applications, but desktop requirements are always significantly higher then individual servers.

> erm? Atomic is for running Docker containers. I'm referring to user-facing stuff like evince, firefox, libreoffice, gimp, etc.

What on earth does it have to do with 'Microservices'? Regardless, the atomic hosts are very stripped down. You are not going to have to worry about firefox vulnerabilities.

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 14, 2015 15:06 UTC (Tue) by rahulsundaram (subscriber, #21946) [Link]

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 14, 2015 15:21 UTC (Tue) by raven667 (subscriber, #5198) [Link]

> I'm referring to user-facing stuff like evince, firefox, libreoffice, gimp, etc. They spew their files all over the file system, mixing in with OS level components. On top of that, a security hole in firefox has the potential to expose all of the user's data.

This problem has had a lot more work put into solving it on the mobile platforms like iOS and Android, to prevent end-users from destroying their phones when installing third-party software, by heavily sandboxing the apps and providing much more restricted APIs for them to communicate with one another and with the OS. This style of user-facing software deployment is no longer experimental but is now a proven standard, unfortunately the number of man-hours it will take to shoe-horn existing software into the sandboxed app-store model means that we are years away from having this be the default on traditional Linux distros.

ChromeOS is probably the leading Linux distro here, one of the few that sells significant amounts of hardware to the non-IT-employee market.

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 15, 2015 4:07 UTC (Wed) by SEJeff (guest, #51588) [Link] (1 responses)

Microservices 101: The good, the bad and the ugly (ZDNet)

Posted Jul 15, 2015 10:03 UTC (Wed) by torquay (guest, #92428) [Link]

Looks like each desktop app was containerized by a bunch of dedicated hand-tuned hacks.

However, it is very cool as an effective technology demonstrator... even PulseAudio was containerized!


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds