SOA - Erfaringer

813 views

Published on

Gjennomgang av et ikke helt vellykket prosjekt. Intregarsjonsproblematikk. SOA

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
813
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

SOA - Erfaringer

  1. 1. Et integrasjonsmareritt
  2. 2. Thordur Arnason Direktør, Teknologi Creuna AS
  3. 3. Case: Automatiser provisjonering av xDSL kunder
  4. 4. Hvor vanskelig kan det være?
  5. 5. 1.1 1.2.1 Check Customer line request (web) 2.1 availability 1.2 Check Book DSLAM last-mile port availability 1 1.2.2 Check 2.2.1 Book Request & distance to line Qualify central 2 2.2 Book 1.3 Credit Initiate last mile check processing connetion customer 1.4 2.2.2 Book Check DSLAM port central prep availability 2.3 Order CPE 3.1.1 Test DSLAM port 3.1 Check last mile and DSLAM 3.1.2 Test Last mile & CPE A-Z Provisioning connection 3 3.2 Complete Remote Config processing CPE 4.1.1 Create POP account 3.3 Write to 4.1 inventory POP and Web setup 4.1.2 Create Web account 4 4.2 Customer CRM export setup 4.3 Create Customer Billing record & Export
  6. 6. 17 manuelle steg 4 eksterne systemer 10 interne systemer Hvorav fem legacy og to ikke ferdigimplementerte
  7. 7. Hvordan kunne det sett ut i en SOA verden?
  8. 8. Internal Systems External Systems Web Portal quot;Customer acquisitionquot; Service Credit-check Inventory system Infrastructure Kapaks Interface quot;Last mile infoquot; DSLAM MQ Provisioning MQ Message broker Engine Message broker Customer Logistics mail & web provider provisioning CPE quot;Big Telcoquot; CC / CRM Last-mile System orders Billing CPE System Interface
  9. 9. Vent nå litt, var dette SOA?
  10. 10. • Service loose coupling • Service contract • Service abstraction • Service reusability • Service discoverability • Service encapsulation • Service composability • Service autonomy • Service optimization
  11. 11. Hvordan var virkeligheten?
  12. 12. Internal Systems External Systems Web Portal quot;Customer acquisitionquot; Service Credit-check Inventory system Infrastructure Kapaks Interface quot;Last mile infoquot; DSLAM Provisioning MQ Engine Message broker Customer Logistics mail & web provider provisioning CPE CPE Interface quot;Big Telcoquot; CC / CRM Last-mile System orders Limited Webservice (SOAP/REST) Billing SOA Webservice System FTP / SFTP Telnet / SSH Unknown Screen scraping
  13. 13. Hva gjør vi nå?
  14. 14. Plan A
  15. 15. Web Portal quot;Customer acquisitionquot; Service Inventory All integrasjon Provisjonerings her arbeidsflyt Infrastructure Interface DSLAM Integration MQ Provisioning engine Message broker Engine Customer mail & web provisioning Standard meldings- CC / CRM utveksling System Billing System
  16. 16. Første feilsteg
  17. 17. Vi undervurderte Web Portal quot;Customer acquisitionquot; integrasjonskompleksisteten Service Inventory Infrastructure Interface DSLAM Integration MQ Provisioning engine Message broker Engine Customer mail & web provisioning CC / CRM System Billing System
  18. 18. La oss tenke en gang til
  19. 19. Web Portal quot;Customer acquisitionquot; Service Inventory Infrastructure Interface DSLAM Provisioning engine Customer mail & web provisioning CC / CRM System Billing System
  20. 20. All singing, all dancing system SOAP H SS R ES t/ ne T l Te Screen Scrape Provisioning FTP engine S SF W T A P SO POP
  21. 21. Det gikk jo riktig så bra, eller?
  22. 22. Integrasjonspunkt Suksessgrad Integrasjonspunkt 1 92% Integrasjonspunkt 2 97% Integrasjonspunkt 3 88% Integrasjonspunkt 4 92% Integrasjonspunkt 5 95% Integrasjonspunkt 6 91% Integrasjonspunkt 7 89%
  23. 23. Litt statistikklærdom
  24. 24. Integrasjonspunkt Suksessgrad Integrasjonspunkt 1 92% Integrasjonspunkt 2 97% Integrasjonspunkt 3 88% Integrasjonspunkt 4 92% Integrasjonspunkt 5 95% Integrasjonspunkt 6 91% Integrasjonspunkt 7 89% Tjenestepålitelighet 56%
  25. 25. Begrenset suksess (om vi velger å se glasset halvfullt)
  26. 26. Hva lærte vi?
  27. 27. SOA er en god idé, men “Don’t boil the ocean!”
  28. 28. SOC er en veldig god idé Vår provisjoneringsmotor endte opp som A BIG BALL OF MUD
  29. 29. A Big Ball of Mud is a haphazardly structured, sprawling, sloppy, duct-tape-and-baling-wire, spaghetti-code jungle. These systems show unmistakable signs of unregulated growth, and repeated, expedient repair. Information is shared promiscuously among distant elements of the system, often to the point where nearly all the important information becomes global or duplicated.
  30. 30. • Service loose coupling • Service contract • Service abstraction • Service reusability • Service discoverability • Service encapsulation • Service composability • Service autonomy • Service optimization
  31. 31. Integrasjon er ingen spøk
  32. 32. Takk for meg! tar@creuna.no http://creuna.no http://tar.vox.com http://twitter.com/tar http://tar.tumblr.com http://linkedin.com/in/thordur http://slideshare.net/tar

×