Service oriented architecture:
Design approach in which multiple services collaborate to provide a certain set of capabilities.
Characteristics service oriented architecture:
Calls across a network
Promotes code reusability
Easier to maintain code
Problems
Communication protocols ( SOAP)
Vendor Middleware
Lack of guidance on where to split your system
Microservices key concepts:
Domain driven design
Loosely coupled
High cohesion of business functionality rather than code functionality
Flexibility
Avoid the mistake of
Using one database for many services
Microservice boundaries:
- Hiding
- comprehensibility
- flexibility
Continuous deployment lack of control of the software cycle :
- new versions being moved from staging to production
- no easily understood numbering or schedule for these frequent deployments
- less time for testing
- buggy software increased instability
- buggy can be reverted
- cannot be used for safety mission critical software kill someone
Continuous integration:
Check in the changes into mainline .
- consistency
- merge conflicts
(Integration hell when they all check in together)
Continuous delivery:
- allowes new functionality to be released as soon as it’s developed
Economic considerations on why delivery may be delayed:
What :
Leap ahead of competitor
Catch up on a competitor
Urgent customer demand
When:
Trade show coinciding
Tie in a marketing campaign
Continuous delivery:
- improvements move automatically and quickly through the development pipeline
- developers happy see work in production
- customer gets improvements they need
