On EDA, CEP and disruptive technology Post: 302252557

Sponsored Content

Special Forums News, Links, Events and Announcements Complex Event Processing RSS News On EDA, CEP and disruptive technology Post 302252557 by Linux Bot on Wednesday 29th of October 2008 08:40:16 PM

10-29-2008

Registered User

On EDA, CEP and disruptive technology

2008-10-29T23:27:00.006+02:00

This is the second time in the last few months that the term "disruptive technology" is being used, this time by Mark Palmer who adds his voice to the EDA vs. CEP discussion. Mark acknowledges the fact that EDA and CEP are not synonyms, but asserting that CEP is the disruptive part of EDA.

Recall that in the Oracle Blog the "disruptive" word was used recently and I have discussed it at that time; Richard Veryard has answered my response claiming that "disruptive" is often not better, at least not in the short run.

Anyway, I have noticed in the recent few weeks, two IBM customers who made plans to move to EDA (neither will use CEP, at least not in the short run). The shift to EDA is a fundamental change in the architecture thinking with the introduction of the decoupled event-driven thinking. Is it new ? - not really. Is it new for these customers - yes, not only new, but a significant change in thinking, it is an indication that there is a beef in EDA, even without introducing CEP, that the enterprise should digest. While thinking in events is natural in the daily life, it is still not natural for enterprise architecture and programming paradigm.

Bottom line -- while CEP certainly has its merits (if the customer has mature enough to digest it), EDA seems to be a more fundamental change in thinking relative to the alternative, and has its own beef. More - Later.

Source...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

LEARN ABOUT MOJAVE

systemd-detect-virt

SYSTEMD-DETECT-VIRT(1)                                          systemd-detect-virt                                         SYSTEMD-DETECT-VIRT(1)

NAME

       systemd-detect-virt - Detect execution in a virtualized environment

SYNOPSIS

       systemd-detect-virt [OPTIONS...]

DESCRIPTION

       systemd-detect-virt detects execution in a virtualized environment. It identifies the virtualization technology and can distinguish full
       machine virtualization from container virtualization.  systemd-detect-virt exits with a return value of 0 (success) if a virtualization
       technology is detected, and non-zero (error) otherwise. By default, any type of virtualization is detected, and the options --container and
       --vm can be used to limit what types of virtualization are detected.

       When executed without --quiet will print a short identifier for the detected virtualization technology. The following technologies are
       currently identified:

       Table 1. Known virtualization technologies (both VM, i.e. full hardware virtualization, and container, i.e. shared kernel virtualization)
       +----------+----------------+--------------------------------------+
       |Type      | ID             | Product                              |
       +----------+----------------+--------------------------------------+
       |VM        | qemu           | QEMU software virtualization,        |
       |          |                | without KVM                          |
       |          +----------------+--------------------------------------+
       |          | kvm            | Linux KVM kernel virtual machine,    |
       |          |                | with whatever software, except       |
       |          |                |             Oracle Virtualbox        |
       |          +----------------+--------------------------------------+
       |          | zvm            | s390 z/VM                            |
       |          +----------------+--------------------------------------+
       |          | vmware         | VMware Workstation or Server, and    |
       |          |                | related products                     |
       |          +----------------+--------------------------------------+
       |          | microsoft      | Hyper-V, also known as Viridian or   |
       |          |                | Windows Server Virtualization        |
       |          +----------------+--------------------------------------+
       |          | oracle         | Oracle VM VirtualBox (historically   |
       |          |                | marketed by innotek and Sun          |
       |          |                | Microsystems),                       |
       |          |                |             for legacy and KVM       |
       |          |                | hypervisor                           |
       |          +----------------+--------------------------------------+
       |          | xen            | Xen hypervisor (only domU, not dom0) |
       |          +----------------+--------------------------------------+
       |          | bochs          | Bochs Emulator                       |
       |          +----------------+--------------------------------------+
       |          | uml            | User-mode Linux                      |
       |          +----------------+--------------------------------------+
       |          | parallels      | Parallels Desktop, Parallels Server  |
       |          +----------------+--------------------------------------+
       |          | bhyve          | bhyve, FreeBSD hypervisor            |
       +----------+----------------+--------------------------------------+
       |Container | openvz         | OpenVZ/Virtuozzo                     |
       |          +----------------+--------------------------------------+
       |          | lxc            | Linux container implementation by    |
       |          |                | LXC                                  |
       |          +----------------+--------------------------------------+
       |          | lxc-libvirt    | Linux container implementation by    |
       |          |                | libvirt                              |
       |          +----------------+--------------------------------------+
       |          | systemd-nspawn | systemd's minimal container          |
       |          |                | implementation, see systemd-         |
       |          |                | nspawn(1)                            |
       |          +----------------+--------------------------------------+
       |          | docker         | Docker container manager             |
       |          +----------------+--------------------------------------+
       |          | rkt            | rkt app container runtime            |
       +----------+----------------+--------------------------------------+

       If multiple virtualization solutions are used, only the "innermost" is detected and identified. That means if both machine and container
       virtualization are used in conjunction, only the latter will be identified (unless --vm is passed).

OPTIONS

       The following options are understood:

       -c, --container
           Only detects container virtualization (i.e. shared kernel virtualization).

       -v, --vm
           Only detects hardware virtualization).

       -r, --chroot
           Detect whether invoked in a chroot(2) environment. In this mode, no output is written, but the return value indicates whether the
           process was invoked in a chroot() environment or not.

       --private-users
           Detect whether invoked in a user namespace. In this mode, no output is written, but the return value indicates whether the process was
           invoked inside of a user namespace or not. See user_namespaces(7) for more information.

       -q, --quiet
           Suppress output of the virtualization technology identifier.

       -h, --help
           Print a short help text and exit.

       --version
           Print a short version string and exit.

EXIT STATUS

       If a virtualization technology is detected, 0 is returned, a non-zero code otherwise.

SEE ALSO

       systemd(1), systemd-nspawn(1), chroot(2), namespaces(7)

systemd 237                                                                                                                 SYSTEMD-DETECT-VIRT(1)