Topaz CETUS 1WMP
• Topaz is the global order management, routing, execution and trade support platform, part of the One Wealth Management Platform.
Based on Java the distributed architecture is designed for high throughput and high reliability with automatic failover in case of software or hardware failures.
that uses UBS’s proprietary, high availability, low latency, zero-GC, Java-based Bluezone technology (event-driven framework using Reliable Multicast Bus on UDP over dedicated LAN) for scalability, fault-tolerance, messaging, and persistence.
• I was initially hired to automate the migration of orders and positions from legacy systems as part of the roll-out of Topaz CETUS to Germany. As I finished the development of that functionality and the project deployment has been delayed for unrelated reasons, I was drafted into reporting on the delivery status of all the outstanding CETUS features, maintaining a
Built a generic web-based facility to dig down into what happened to an order and its related records throughout its lifetime.
Worked on introducing Topaz to Germany as the developer responsible for automating the migration of orders and positions from the legacy systems, also had Business Analyst and Project Manager responsibilities and supported the switch-over.
Topaz is a high availability, low latency, event‑driven system based on Reliable Multicast Bus infrastructure. Worked on the Topaz introduction to Germany as the developer responsible for automating the migration of orders and positions from the legacy systems, but also had Business Analyst and Project Manager responsibilities: liaised between business users and developers to analyze requirements and develop technical solutions, prioritized tasks, tracked deployment of changes into production, investigated issues.
The system uses standalone Java applications running as microservices with multiple instances across two geographically separated data centres for fault tolerance and failover. The microservices communicate on the Bluezone dedicated LAN, as well as JAXWS SOAP-based web services. The development was very fast-paced, small changes to individual microservices could be deployed into production at any time during the week, and if problems arose, those were fixed in a very timely manner with the motto "we don't roll back, we roll forward".
Shared best practices by developing common tools and publishing a list of HowTos.
Responsibilities: Hands-on technical lead, Design and development of framework and core system features in Java/Linux