Microservices

The Ignite Broker platform provides a lot of functionality. That’s great, but it’s not always all relevant to our clients. The modern insurance broker needs to acquire best-of-breed software and that means picking and choosing functionality from different providers.

To allow brokers to do this Ignite Broker is built in a modular fashion. Brokers can choose which modules they need and substitute out or enhance ones that they can get elsewhere.

For example a broker might already have a great customer journey and website. No problem: Ignite has an API for that and the broker can use the Ignite policy administration and rating functions without changing their website.

Another example: a client might already have a rating engine (internal or external) that holds their pricing algorithms. Ignite’s policy administration system can simply call to this new rating engine as well as the Ignite proprietary one.

Most recently Ignite has been chosen to provide the Ignite Accounting module for a major broker platform supporting over £180m of premium. APIs between Ignite and the client mean both systems can run and be deployed independently, with loose coupling, and remain highly maintainable and resilient.

How is this done? Rather than having a large system that relies on all its parts to function, Ignite Broker is a series of smaller services that talk to each other, also known as “microservices”. Think of it like a honeycomb, where each of the cells are built on one another; independent but also integrated. For each cell we use the best available tech and, when something better comes along we crack the wax seal (as it were) and substitute in something better.

Some of our microservices include: rating engine, customer portal, commissions, complaints, and more.

If you’d like to read more about microservices go here

If you’d like a demo of the Ignite honeycomb (sort of), go here