IOOF Mongodb Australia
2 likes399 views
- IOOF is an Australian financial services company founded in 1846 that offers products like financial advice, superannuation, investment management, and trustee services. - It has 235 IT employees across the group working on corporate systems, platform systems, and infrastructure services. Platform systems include multiple vendor-supplied, internally developed, and retail vs employer systems. - In 2009, IOOF started using Agile development and now releases new features 50-100 times per month through cross-functional teams to address issues of the past like vendor lock-ins, scalability problems, and siloed systems.
Ad
More Related Content
What's hot (20)
Similar to IOOF Mongodb Australia (20)
Ad
More from MongoDB (20)
![MongoDB .local San Francisco 2020: Powering the new age data demands [Infosys]](https://cdn.slidesharecdn.com/ss_thumbnails/315pminfosysfinalsfoversionvocalpart1-200120221508-thumbnail.jpg?width=560&fit=bounds)
Ad
Recently uploaded (20)
![Download Wondershare Filmora Crack [2025] With Latest](https://cdn.slidesharecdn.com/ss_thumbnails/neo4j-howkgsareshapingthefutureofgenerativeaiatawssummitlondonapril2024-240426125209-2d9db05d-250419-250428115407-a04afffa-thumbnail.jpg?width=560&fit=bounds)
IOOF Mongodb Australia
- 1. Presented by IOOF IT System’s Modernisation Damien O’Donnell 6th & 8th June 2017
- 2. 2 IOOF in brief IOOF Holdings Limited is an Australian financial services company which offers a range of products and services including financial advice, superannuation, investment management and trustee services. It was founded in 1846 as the Victorian branch of an international friendly society, and has its origins in the provision of sickness and funeral benefits prior to the widespread availability of government-funded welfare services.
- 3. 3
- 4. 4 Information Technology (size / scale) • 235 FTE across the group • 154 FTE working on ‘Platform Systems’ • 7 FTE working on ‘Infrastructure Service’
- 5. 5 Types of Systems • Corporate Systems • email • office • browsers • file system • AD • etc • Platform Systems (multiple) • vendor • intern developed • retail v employer • Business Systems • vendor supplied - generally • CRM • financial planning tools • CMS • stock broking • etc
- 6. 6 State of the world (2009) • multiple admin platforms • $$$ • slow features releases • single vendor lock in’s • M&A • scalability issues + hard limits • monolithic
- 7. 7 Changed the way we work • started ‘Agile’ in 2009 • continues delivery • 50 – 100 release a month • highly flexible environment • cross functional teams (2013) • 13 delivery teams
- 8. 8 Why we work this way?
- 10. 10 Interface Storage Deployment Data FeedsThick Client Runtime MySQL MongoDB ElasticrabbitMQ Kafka Storage ASIS Adviser Web Member Web UX Indentity Transaction Engine Trade Engine Income Distribution Core (headless) Balance Engine Authenticator Retail Insurance Standing Instructions Search Engine Fees Engine Etc .. Services / Applciations Balance Engine Tax Engine Unit Price Insurance Premium InvestmentSuper Stream Analytics Load Balance Logging Security Monitoring Server Provisioning Email SMS Infrastructure Services API Platform Systems Concept
- 11. 11 Micro Services • Why? • incremental improvement – evolution v revolution – complex problems • continues delivery – ripple effect of change / release • technology scale • work force scale – decoupling good for complex domains • flexibility – M&A • future integration • HA • technology generational gap • Learnings • admin fee (April 2012 – released November 2012) • scale issues (https) • multiple instances / scaling • proxy • areas to standardize – languages – queues – logging – APM – DB’s – configuration – build / deploy
- 12. 12 Micro Services • ‘a complex arrangement of simple things’ • 220 and growing …
- 13. 13 Document Storage • relational v document • simple domain representation • forces ‘correct patterns’ for development teams of micro services • storage / state for micro services • data warehouse
- 14. 14 Why MongoDB? • evaluated (CouchDB, Cassandra DB, Neo4j, MySQL & MongoDB) • MongoDB • ‘most enterprise’ • didn’t need a graph DB • fast • low cost of adoption • learnings • 30 databases / size • ops manager • schema maintenance (3.2 mongoTrek) • wired tiger • provisioning
- 15. 15 Trade Notification Service MySQL Business Event (Kafka) Equity Trade Gateway Trade Validation Service (API’s) MongoDB Trade Transaction Service Group Order Submission Service Investment MySQL Transaction Service Order Repository Service MongoDB ASIS External Markets RightFax CalastoneIRESS Order Service GBST (SQL Server) Listed Confirmation Service Queue Event (RabbitMQ) MongoDB for micro services state
- 16. 16 Account Retrieval Service MySQL Data Warehouse (MongoDB) CDC Event (Kafka) Account State (Kafka) ForkLift Service Elastic Search (API’s) Transaction State (Kafka) Transaction Retrieval Service Portfolio Transaction Service Replication Log Maxwell Portfolio Job Manager Portfolio State (Kafka) Portfolio Bulk Loader Portfolio Balance WorkerResults (RabbitMQ) Tasks (RabbitMQ) BDN Retrieval Service Insurance Retrieval Service (API’s) MongoDB for Data Warehouse
- 17. 17 API’s • open API’s • multiple validations (consumer responsibility v user feedback) • business logic • business 2 business integration • documentation – human readable • security (OAuth2 like) • fault tolerant – contain technical domain complexity • separation of concerns / boundaries • scale • SOAP v (Rest + JSON RPC)
- 18. 18 Web interfaces (secure) Tax Engine Trade Engine Portfolio Service Dev Team 1 Dev Team 2 Web User Interface
- 19. 19 Application Infrastructure Provisioning API Core I Requests a server (iatool) IPAM Open Net Admin DNS Window s Red Hat Satellite External Services Restful API Job Queue Database Contains machines data Internal Services Zones Machine Names Environments Sizes Requests an Instance Bootstraps • Redis Queue to queue jobs Window s Active Director y Provisioning API
- 20. 20 Application Infrastructure • Machine provisioning • Application deployment • Supporting • development / sandbox x 12 • production x 1 • staging x 1 • DR x 1 (cold, 1 hour to build) • 220 ‘ish micro services in each + queues + databases • 239 production machines • 830 development machines • 54,000 machines provisioned since February 2014
- 21. Questions 21 Please come and see me afterwards!