IJYI

Menu

Why messaging?

In a world of cloud hosting and software as a service, integrating business and enterprise systems poses significant challenges. The days of a single vendor application or hosting stack are gone. The agility afforded by software as a service is now expected across systems.

Designing and building applications for scale whilst continuously delivering value also poses significant challenges for development. Co-ordinating the processing of messages, whilst working on complex business logic, means that developers often need to keep their heads in two different worlds and balance two different business needs.

We developed the IJYI Messaging Pipeline (IMP) to enable our internal development team to concentrate on what mattered to our customers, delivering business value, safe in the knowledge that the co-ordination and processing of messaging events is handled by the IJYI Messaging Pipeline.

Range of cloud transports supported

Support for Redis, Amazon SQS, Microsoft Azure Service Bus and Apache ActiveMQ gives huge flexibility on where your messaging platform is hosted.

Minimal development learning curve

IMP was created to allow our internal development team to concentrate on the business logic of an extremely complex software build, without having to worry about the underlying transport of the distributed messages they were creating.

Fast, resilient, built for the cloud

The IJYI Messaging Pipeline has been built from the ground-up for the cloud, supporting both AWS Simple Queuing Service (SQS) and Simple Notification Service (SNS), as well as Microsoft Azure Service Bus.

Used in conjunction with autoscaling services that these cloud platforms provide, this affords significant cost savings, whilst allowing message handling nodes to spin up according to workload.