API優(yōu)先策略如何幫助企業(yè)真正實現(xiàn)數(shù)字化

1、API優(yōu)先策略如何幫助企業(yè)真正實現(xiàn)數(shù)字化 2015 Axway|Confidential2 2015 Axway|Confidential“To Improve Is toChange; To Be Perfect Isto Change Often”Sir Winston Churchill提高就是要改變,而要達到完美就要不斷改變。 2015 Axway|Confidential3Weve already been forced to change 2015 Axway|Confidential4Digital Business has no Border Architecting forM

2、obile isnt enough Omni-channelexperiences requirea new approach Digital products areKing 2015 Axway|Confidential5Expectations for IT have changed In the past enterprise architecture was designed forknown use cases and integrations The consumer cloud & mobile application model haschanged the way

3、business users view IT products andprocesses Todays enterprise must architect for the unknown Enterprise IT systems are no longer an island andmust build their capacity to integrate with the outsideworld 2015 Axway|Confidential6|7Netflix has shown the wayReactions Adrian Cockcroft received.“You guys

4、 are“What Netflix is doingwont work”-2010“Wed like to dothat, but cant”-2012Confidentialcrazy! Cantbelieve it”-2009“It only works forUnicorns like Netflix”-2011 2015 Axway 2015 Axway|Confidential8A mandate for change! 2015 Axway|Confidential9Enterprise IT Adoption Cycle - Simon WardleyClients 2015 A

5、xway|Confidential11What do Enterprise Applications looklike?Backend ServerDataStorageWebClientMobileClientOtherOtherClients 2015 Axway|Confidential12The backend relied on monolithicapplications All functionality in a singleprocess Scale by adding serversBackend Server 2015 Axway|Confidential13SOA in

6、troduced separation Separable elements of functionality become services Scale & reuse services as neededBackend ServerServiceServiceServiceService 2015 Axway|Confidential14Are these services useful?The value of a well-designedobject is when it has such a richset of affordances that the peoplewho

7、 use it can do things with itthat the designer neverimagined.”Donald Norman 2015 Axway|Confidential15Are these services useful?Are these services able to servetodays application needs?And tomorrows? 2015 Axway|Confidential16Introducing Microservices“the microservice architectural style. .is anapproa

8、ch to developing a single application as a suiteof small services, each running in its own process andcommunicating with lightweight mechanisms, often anHTTP resource API. ”Martin Fowler :/martinfowler /articles/microservices.html 2015 Axway|Confidential17BackendServerServiceServiceServiceServiceWhy

9、 Microservices? A platform for the business Agility Not tied to technology 2015 Axway|Confidential18Loosely CoupledIts not looselycoupled, if multipleservices need to beupdated at thesame time 2015 Axway|Confidential19Functionally BoundedYou should notrequire too muchinformation aboutsurroundingserv

10、ices 2015 Axway|Confidential20Sounds familiar? 2015 Axway|Confidential21Are these services useful?How small is microservice?We want to avoid dumb servicesthat are just CRUD wrappers 2015 Axway|Confidential22SOA vs MicroservicesSOATeam focused onservicesServices deployed in ashared busMachine readabl

11、eservice registryCentralizedorchestrationCentralized datastorageMicroservices Teams aligned withbusiness Services deployed at theedge Developer readablecatalogue Orchestration within eachapp Data storage replicatedacross atomic instances 2015 Axway|Confidential23Build it, Run it, Own it SOA Services

12、 were seen as projects The team moves on when the scope of that project isdelivered Microservices and their APIs must be managed asproducts Product team owns their service from conception toretirement 2015 Axway|Confidential24 2015 Axway|ConfidentialExamining the componentsof a microservicesarchitec

13、ture 2015 Axway|Confidential25Defining Services 2015 Axway|Confidential26Defining Services Build services for business functions not knownintegration problems Implement a process to build and deploy eachservice independently Existing services can be maintained, while new orpartial services are launc

14、hed No impact to production until traffic routing is updated 2015 Axway|Confidential27Decentralize Everything 2015 Axway|Confidential28Decentralize Everything Developers can build services on any platform, withany tools Limit or remove centralized resources Databases Message Queues Enterprise Servic

15、e Buses 2015 Axway|Confidential29High Trust, Low Friction 2015 Axway|Confidential30High Trust, Low Friction Developers dislike rebel against strict governanceprocesses Services should be managed and owned by productteams Lifecycle management Functional decomposition based on the business Services sh

16、ould not represent technology or architecturalconstraints, but rather business requirements 2015 Axway|Confidential31Lightweight Integration Patterns 2015 Axway|Confidential32Lightweight Integration Patterns Services should be stateless Hide backend implementation complexity Document your services a

17、nd their APIs Swagger, RAML, Blueprint 2015 Axway|Confidential33Think Differently About API Design 2015 Axway|Confidential34Think Differently About API Design Bring the Web to enterprise integration Traditional RPC-style APIs can depend on a highdegree of context for surrounding services Design a RE

18、STful representation of your service This API should look at application needs (outside-in) Hypermedia-Style APIs promote loose-coupling Use HTTP linking to self-document service capabilities 2015 Axway|Confidential35Design security with public access inmind 2015 Axway|Confidential36Design security with public access inmind Access to services must be managed Dont assume internal or private access Define or in