In this edition of Solace Says, I interviewed Jonathan Schabowsky of Solace's office of the CTO, who recently wrote a blog post about event-driven microservices that's turned out to be quite popular. In that post, and this video, Jonathan describes the characteristics most microservices share, what they're commonly used for, and how they share information with REST and/or messaging technology.
Today, many financial institutions hire 3rd-party settlement agencies (like CLS) to ensure the integrity of these transactions, trusting them to identify and rectify situations where things go sideways, whether innocently or intentionally. Each company has a team that deals with reconciling these discrepancies. Including these agencies in the high-volume flow of transactions is important, but adds considerable complexity to the flow of information, and can be quite expensive.The opportunity to fix this glaring market inefficiency is what has so many people in the financial services industry excited about blockchain-based ledgers: a single source of truth that all counterparties can see and trust. No more arguments, no more intermediaries. A distributed, shared, governed ledger based on blockchain effectively establishes shared purpose-specific back-office infrastructure that can streamline and reduce the cost of conducting transactions.
Let me share with you some good news for developers interested in trying out or getting started on the JMS standard based features of the Solace Message Router with Solace JMS: After installing and starting a Solace Virtual Message Router (VMR), it will now take you less than a minute to get from zero to having a working JMS sample code fetched from GitHub, all built and running to get your first JMS message exchanged with the Solace Message Router. With the Solace APIs Now Available via Maven Central, the build will automatically pull down the required Solace JMS client libraries.