Intigua Virtualizes All Your System Management Agents

(Excerpt from original post on the Taneja Group News Blog)

Imagine if all your heavyweight system management agents suddenly became super-stealthy and were no longer at risk of being caught directly deployed in a virtual machine. Imagine that all your agents across solutions could be managed, even orchestrated, from one console. And they no longer put their target machines at risk while getting their special kernel access missions on each vm accomplished safely and securely.  

This sounds like a combination of cold war espionage, cyberpunk fiction, and remote drone warfare. But Intigua, coming out of semi-stealth mode  today, is claiming that they will virtualize your whole set of system management agents including those for performance, security, and backup. A virtualized agent can then be executed on each target virtual machine without having to be installed on it. Because of their remote operational control, Intigua can orchestrate a set of agents to prevent agent overload or interference, and can throttle total agent utilization to prevent  management overhead from impacting performance or availability.

Having worked in systems management for many years, I’ve had to install thousands of agents at some of the biggest Fortune 1000 production environments (once upon a time even by mounting a portable tape drive to each machine in turn…). Intigua’s single image agent management alone sounds like nirvana. When you factor in how it can be hard if not impossible to stage management agents in linked clones or golden vm images, that you can’t make use of app virtualization for system-level agents, and find software deployment solutions for complex agent processes difficult to script in a bullet-proof consistent way, the potential value of agent virtualization to large enterprises and cloud service providers grows significantly.

There are many more potential benefits to virtualized agents including ensuring better compliance, more fully automated provisioning, and painless agent updating. I’d be surprised if Intigua hasn’t already been noticed by one or more of the Big 4 systems management companies.  “Systems management virtualization” could instantly revitalize some increasingly legacy management solution portfolios. If Intigua’s solution works as claimed, powerful full agents could make a real come-back against compromised agentless solutions. 

…(read the full post)

A SQL Sequel Called TED – the Distributed TransLattice Elastic Database

(Excerpt from original post on the Taneja Group News Blog)

While the focus in databases recently has been on exciting NoSQL variants designed to tackle big data challenges or build transformational web scale apps, most enterprise applications still have mandatory requirements for transactional (ACID) properties keeping them tied to traditional relational database architectures. However, businesses are feeling pressured to evolve their transactional database solutions to enable highly available, “local” application access to globally consistent data.

Global IT shops face a big challenge in distributing relational data, as most approaches to-date have large implementation and operational overhead costs, and often involve serious trade-offs between local access and global consistency. Adding to the burden, local governments might have laws about ensuring data “location” compliance that absolutely must be met.

TransLattice started out delivering an appliance “platform” for distributed business computing. Due to popular demand, they’ve unhinged the database and launched that as its own solution called the TransLattice Elastic Database, or TED for short. Although calling your database TED seems a bit informal, the underlying implementation based on PostgreSQL is anything but. TED’s fully ACID/SQL relational implementation is designed to be logically and geographically distributed, providing policy-driven controls for each table’s replication. Transactions are automatically brokered and routed on the client side to ensure local performance and high availability, with a distributed commit algorithm on the backend to ensure global consistency. When nodes become unavailable, they get routed around, and when back online, automatically get updated.

TED database nodes can be TransLattice appliances, virtual machines, cloud based instances, or even all of them at once as access, availability, and performance needs dictate. TED nodes can be launched in Amazon EC2 for instance. Nodes can be added to the database dynamically, and data will automatically get distributed according to policy or performance needs.

The best part is that SQL applications don’t have to be modified or become aware that TED isn’t just the same old local SQL database.  Since it drops in, scales easily and cost-effectively, and instantly increases global reach and availability, we think TED will go far.

…(read the full post)