SOA e IMS (NGN)
•Transferir como PPT, PDF•
1 gostou•660 visualizações
Apresentação feita em 2006, evento IMS (IQPC), no Rio de Janeiro, Brasil.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (17)
Semelhante a SOA e IMS (NGN)
Semelhante a SOA e IMS (NGN) (20)
Último
Último (20)
SOA e IMS (NGN)
- 1. IMS e SOA: Reduzindo o Tempo de Implementação de Novos Serviços Palestra realizada em Julho/2007 – Davi Carvalho (CIO) http://soasimples.com
- 2. IMS I P M ultimedia S ubsystem http://soasimples.com
- 5. I M S PoC MMS IP TV GLM P2P Game VoIP Enabling Sevices Devices Applications IP Multimedia Subsystem Networks IMS: Simplified Architetcure http://soasimples.com WLAN GPRS ADSL
- 6. Rede NGN / IMS Compliant SBC Sype Server ATA Gateway H.323 IP PBX PSTN Media Gateway ControlSwitch http://soasimples.com
- 8. S ave O ur A rchitecture http://soasimples.com
- 9. Service-Oriented Architecture “ SOA is a IT architecture strategy for business solution (and infrastructure solution) delivery based on the concept of service-orientation.” http://soasimples.com
- 10. "By 2008 , SOA will be a prevailing software engineering practice, ending the 40-year domination of monolithic software architecture." http://soasimples.com
- 11. Infrastructure Platform HW OS Cluster Grid Application Services Third-Party Services ESB – Enterprise Service BUS Data Access Services Access Services Collaboration Services Orchetration Services Service Control Serv. Reg. Repository Ident & Access Mgmt. Service Monitoring Business Activity Monitoring Service Deployment Integr. Sw Environm. Service Design Service Developmt Service Registry Repository Change Mgmt SOA Reference Architecture http://soasimples.com
- 13. “ Silo” App. “SOA” App. http://soasimples.com
- 14. IMS “Silo” Applications Application 1 Customer Data Media Functions Service Delivery Plataform Application 2 Customer Data Media Functions Service Delivery Plataform Application N Customer Data Media Functions Service Delivery Plataform Billing ERP CRM Pre-Paid ... http://soasimples.com
- 15. Application 1 Customer Data Media Functions Service Delivery Plataform Application 2 Customer Data Media Functions Service Delivery Plataform Application N Customer Data Media Functions Service Delivery Plataform SOA Approach Billing ERP CRM Pre-Paid ... service_D service_A service_B service_C service_E service_F Service Repository Service Repository http://soasimples.com
- 16. DB E S B A P I CDRs FTP Server Billing ERP CRM Pre-Paid CDR Import LCR ... Service 1 Service 2 Service N ... IMS “SOA” Applications ControlSwitch http://soasimples.com
- 17. IMS Services and SOA Environment http://soasimples.com
- 18. Deploying IMS Services SOA: Service-Oriented Architecture EDA: Event-Driven Architecture BPM: Business Process Management + + http://soasimples.com SOA EDA BPM
- 19. SOA: Conventional Request/Reply Service Consumer Service Producer Request Response http://soasimples.com
- 21. source: IBM (http://www-128.ibm.com/developerworks/webservices/library/ws-soad1/) BPM: Business Process Management http://soasimples.com
- 22. ATA Reseller CRM Suply Warehouse Installation Phone Bil Service Orchestration => Business Flexibility http://soasimples.com
- 25. Questions & Answers http://soasimples.com
- 26. Obrigado! Davi Carvalho http://twitter.com/davisilva http://soasimples.com
Notas do Editor
- Operational Data Consistency Gartner defines an ESB as a messaging infrastructure that connects and unifies interactions between services in an SOA. In other words, the ESB enables "plug and play" communications between SOA services. Yet an ESB by itself does nothing to ensure that data interdependencies between services are handled properly. A traditional application is usually deployed as a "silo," meaning the application has its own database that contains a copy of operational business data needed by that application such as customers, products, and inventory levels. Typically, each data silo gets synchronized only periodically, so between synchronizations each silo has slightly different data. These data inconsistencies can cause business errors when silo applications are integrated using an ESB. When silo applications are turned into services, each with different inventory data, you encounter problems (see Figure 2). In this example, the "show status" service thinks that the inventory level is 27, while the "check_avail" service thinks that the inventory level is 0.