David Mavashev

David Mavashev, CEO of Nastel, is a leading expert on IT infrastructure, middleware and messaging technologies with over 25 years experience architecting systems and solutions. His areas of expertise encompass implementing middleware-centric architectures and the underlying infrastructure monitoring that is fundamental for its optimal performance, as well as tools and technologies for monitoring and managing integrated application processes and performance across the enterprise, and helping companies achieve business agility through effectively aligning IT with business processes in the real-time enterprise.

A successful entrepreneur, David founded Nastel in 1994 and also served as the company's CTO for many years. Prior to that, he was the technical manager of the messaging group at NYNEX, where he architected and managed the implementation of the first commercial transactional messaging product, which now forms the basis for IBM WebSphere MQ (formerly MQ-Series). A pioneer in the early evolution of messaging technologies, David logged many years as an IT consultant working with some of the world's foremost banks and financial institutions.

It's likely you've been working with WebSphere MQ (WMQ) for years developing,
deploying, monitoring, or all of the above. It's also likely that by now you
have assembled a tool bag full of items to support your implementations and
ongoing operations. And you've no doubt become accustomed to dealing with
problems within the MQ domain. But what if you could see more of the
transactional journey on either side of MQ? Organizations doing this are
finding new ways to improve levels of service and avoid costly upgrades.
Initially, just seeing the touch points, you know - the "puts" and the "gets"
­ along with MQ administration probably seemed entirely sufficient in order
to manage WMQ. A common assumption was that as long as we saw messages coming
and going, things were okay. Analogous to Archimedes' principle of water
displacement, the health of MQ or any other middleware... (more)

Ultimately, CIOs decide how best to manage their IT infrastructures to
guarantee a quality of service to end users while staying within the
allocated budget. Using a shared services approach for APM fits best in line
with these goals. This approach can provide quality of service to all of the
application owners and drastically reduce the cost.
As a general rule, corporations have multiple groups of application owners.
The common practice is for each application owner to decide the APM solution
required for their particular need at the time. To research the solution, one
or more ... (more)