Proposta Recebida

wwwACloudFancom httpacloudfancom Pragmatic Paths Inc 2021 Contact rajacloudfancom Discount Link to course httpswwwudemycomcoursedomaindrivendesignandmicroservicesreferralCodeC5DCD3C4CC0F0298EC1A Section Development Environment Setup Course Domain Driven Design Microservices for Architects Follow along to setup your environment Dev Environment Setup 1 IntelliJ IDE 2 Project Repositories Branches 3 UML diagram with PlantUML wwwACloudFancom Integrated Development Environment IDE IntelliJ Community Edition but others IDEs are fine too httpswwwjetbrainscomideadownload wwwACloudFancom Git Repositories Code UML models httpsgithubcomacloudfanMSFAACMESalesv10git httpsgithubcomacloudfanMSFAACMEProductsv10git Each Repository to be setup in a separate IntelliJ project wwwACloudFancom Gradle for dependencies Build automation tool buildgradle httpsgradleorg wwwACloudFancom Organization of Code Code is organized in multiple branches Switch to appropriate branch as instructed UML available under the directory uml wwwACloudFancom UML Modelling Course uses UML for modelling the microservices wwwACloudFancom Plant UML httpsplantumlcom Plant UML is used to draw UML diagrams using a human readable text description It is a drawing tool NOT a modelling tool as it does not enforce any modeling constraint wwwACloudFancom IntelliJ Extensions Extension for UML models wwwACloudFancom Plant UML Extension Issue httpsplantumlcomgraphvizdot Plant UML has a dependency on GraphViz library Issues with PlantUML extension after the installation please follow instructions at the link below to install the Graphviz Quick Review Development environment setup Project should not be showing any errors UML diagrams are showing up Microservices Architecture Domain Driven Design What is Microservices Architecture What does an organization need to adopt MSA Benefits of adopting Microservices architecture Microservices Architecture Domain Driven Design What is Microservices Architecture What does an organization need to adopt MSA Benefits of adopting Microservices architecture Benefits of Microservices Why should an organization adopt Microservices Technical Benefits Business Benefits Adoption of MSA IT Teams need support from Business IT Leaders Leaders need to be educated Leaders should see clear value Objective is to build support and commitment for adoption of MSA Microservices 1 Introduction to Microservices 2 Business Digital Transformation 3 Business benefits of Microservices 4 Building a business case for Microservices Section objective 5 Approaches for building Microservices applications Arranging an app as a set of independent services Microservices Architecture 1 Monolithic Architecture 2 Microservices Architecture 3 Realization of MSA wwwACloudFancom Characteristics Monolithic Architecture Teams organized by technology business Modular Huge code bases Changes require coordination between teams Spans across multiple business functions A traditional way of building applications Tight coupling between components wwwACloudFancom Microservices Architecture Arranges an application as a collection of loosely coupled services In a microservices architecture services are fine grained and the protocols are light weight Wikipedia wwwACloudFancom Microservice A service in a MSA is referred to as a Microservice Self contained units built to realize a specific business capability Orders Shipping Marketing wwwACloudFancom Microservice A service in a MSA is referred to as a Microservice Self contained units built to realize a specific business capability Retail Accounts Credit Cards Loans wwwACloudFancom Business capability Microservice May be realized by one or more Microservice Orders Partner Order Service Customer Order Service wwwACloudFancom Since Microservices are organized around business capabilities discovering the optimal domain boundaries is essential to ensure independent nature of the services Domain Driven Design Bounded Contexts Well defined business capability boundaries wwwACloudFancom Microservices Contracts All interactions are via welldefined contracts Ship Order order details Update Status delivery details Orders Shipping wwwACloudFancom MSA Realization Identify business capability domain boundaries 1 Map the domain scope to Microservices 2 Assign ownership of each service to a team 3 Teams coordinate to define contracts ie interactions 4 wwwACloudFancom MSA Realization Demarcate Business Capability boundaries Develop Domain Model Map each capability to one more MS Assign a small team to each Microservice Teams define contracts Design and Release Microservices Domain Driven Design Bounded Context Domain Driven Design Strategic patterns Tactical patterns wwwACloudFancom Business Benefit of MSA Helps the business change at a faster pace Transformation A thorough or radical change in form or appearance Business Transformation MSA 1 Business Digital Transformation 2 Why do businesses need to transform 3 How does MSA enable Transformation wwwACloudFancom Business Transformation Business Transformation is an umbrella term that is used for referring to fundamental changes in how an organization conducts its business Packaged Software to Subscription model wwwACloudFancom Business Transformation Business Transformation is an umbrella term that is used for referring to fundamental changes in how an organization conducts its business Online Bookstore to Marketplace wwwACloudFancom Business Transformation Business Transformation is an umbrella term that is used for referring to fundamental changes in how an organization conducts its business Computers to iPod iPhones iPad Music Store wwwACloudFancom Why do businesses transform Environmental changes eg new regulations Competitive pressure eg rapid rollout of new products New opportunities eg innovative technology Customer demands eg expects immediate response wwwACloudFancom Examples Continuous changes Diversification New products services wwwACloudFancom Digital Transformation Digital Transformation is the process of using digital technologies to 1 meet the needs of transformed business processes 2 create innovative customer engagement mechanisms wwwACloudFancom Digital Transformation Digital Transformation supports the Business Transformation initiatives wwwACloudFancom Digital Transformation Reimagining of business in the digital age is digital transformation Examples TARGET NETFLIX Capital One BEST BUY wwwACloudFancom wwwACloudFancom Digital Transformation Integrated supply chain inventories across network Heavy use of AIML API Analytics etc Physical bank to a digital bank wwwACloudFancom What happens to businesses that do not transform wwwACloudFancom Failed to transform its business in time to counter the threat posed by Netflix newer digital technologies 1997 Started a inmailDVD subscription model 2007 Started streaming service using digital wwwACloudFancom Netflix started a subscription model for DVD by mail in 1997 Netflix started streaming service in 2007 It rapidly transformed its business by leveraging the new digital platforms wwwACloudFancom Continuous Transformation Transformation is not a onetime initiative Businesses need to change on a continuous basis Rapid changes are needed in systems and applications Organizations need to keep up pace with new and evolving technologies wwwACloudFancom Example Continuous Transformation Continuous change Adoption of digital technologies Amazon Prime Amazon Web Services Alexa Appstore Amazon Drive Echo Kindle Fire tablets Fire TV Video Kindle Store Music Music Unlimited Amazon Digital Game Store Amazon Studios AmazonWireless wwwACloudFancom Transformation and Software Old ways of building software hinders transformation Changes are slow Hard to integrate with newer digital technologies Microservices Architecture addresses these challenges wwwACloudFancom HOW does MSA help Change isolated to a set of Microservices Retail Accounts Credit Cards Loans Mortgage Transformation of Credit Cards requires changes only in this MS Thus Bank can achieve its transformational goals at a faster pace Quick Review Organizations need to continuously Transform Rapid changes to IT systems Rapid adoption of new digital technologies Speed to market is the key Microservices architecture enables transformation Business benefits of adopting Microservices Architecture MSA Business perspective 1 Microservices teams 2 Business capabilities and Microservices 3 Business benefits of MSA wwwACloudFancom Microservice Ownership Each service is built operated by a small team Shipping Orders Teams are cross functional supported by domain expert wwwACloudFancom TwoPizza Teams We try to create teams that are no larger than can be fed by two pizzas we call that the twopizza team rule said Bezos httpsdocsawsamazoncomwhitepaperslatestintroductiondevopsawstwopizzateamshtml Team size 8 wwwACloudFancom TwoPizza Teams httpsdocsawsamazoncomwhitepaperslatestintroductiondevopsawstwopizzateamshtml Better collaboration among smaller teams Frequent Software Releases Faster response to changes in business Tech becomes a competitive edge wwwACloudFancom Why are MS organized around business capabilities wwwACloudFancom Why organize around business capabilities Each service can evolve independently Bank will be slow to release new products in the market L Retail Accounts Credit Cards Loans Mortgage wwwACloudFancom Why organize around business capabilities Each service can evolve independently Retail Accounts Credit Cards Loans Mortgage FASTER response to changes in business wwwACloudFancom Why organize around business capabilities Makes it easier for IT Teams to understand the business IT Teams dont need to dive deep into ALL business capabilities Retail Accounts Credit Cards wwwACloudFancom Why organize around business capabilities HIGHER Alignment with business priorities No time spent on managing conflicting priorities New release every 2 Weeks New release every Day wwwACloudFancom Why organize around business capabilities Services are easily replaceable No impact on other services if contracts are not changing wwwACloudFancom Microservices Architecture Microservices Architecture is an enabler catalyst for continuous business transformation Key to rapid transformation faster speed to market IT teams move at the same speed as the business wwwACloudFancom Critical Success Factor Carving out the business scope of Microservices If NOT done correctly Teams will be interdependent Loss of advantage of MSA This is where Domain Driven Design comes into picture wwwACloudFancom Business benefits Faster response to changes ie better agility Easier to build and maintain Improved productivity quality Services are replaceable with zero minimal impact Quick Review Microservices are organized around Business capabilities Small Teams Faster speed to market Enables the IT Teams to operate independently MUST carve out appropriate business scope to stay independent Pros Cons of Microservices MSA Technology Perspective 1 What is a Microservice Architecture 2 Pros of MSA 3 Cons of MSA wwwACloudFancom Microservices Architecture B A C Loosely coupled set of services Services interact over network Light weight protocol HTTP Independent codebases deployments Decentralized governance Well defined business scope wwwACloudFancom Loose coupling Services are loosely coupled Least amount of dependency between services ONLY external interfaces are known to consumer services Interactions are over the network wwwACloudFancom Service interactions Services expose interfaces as APIHTTP wwwACloudFancom Service interactions Messaging is commonly used A B D C wwwACloudFancom Advantages of Microservices Architecture wwwACloudFancom Pros of MSA Changes are easier to manage Regression testing needed ONLY for changed service No impact on other services No Minimal coordination with other teams wwwACloudFancom Pros of MSA Deployments are independent Each team controls the frequency of deployments Higher productivity Faster delivery wwwACloudFancom Pros of MSA Polyglot microservices Each team may decide on tech stack Some experts urge caution against using too many languages Shipping Orders wwwACloudFancom Pros of MSA Failure isolation Failure in one service will not bring down entire system Orders held as messages in a stream Orders Shipping wwwACloudFancom Pros of MSA Failure isolation Failure in one service will not bring down entire system Orders Shipping Orders processed by the service wwwACloudFancom Pros of MSA Service Scalability Each service can scale independently Orders Shipping Orders Orders wwwACloudFancom Disadvantages of Microservices Architecture wwwACloudFancom Cons of MSA Poor performance due to network overheads Orders Shipping Inventory HTTP Messaging wwwACloudFancom Cons of MSA Complexity in managing data integrity Each Service manage its own Database Traditional Tx mechanisms dont work Orders Shipping Inventory HTTP Messaging wwwACloudFancom Cons of MSA Harder to monitor debug wwwACloudFancom Cons of MSA Requires investment in new technologies Infrastructure Tools Skills development wwwACloudFancom Cons of MSA Security threat Each service exposes interfaces API Expanded attack surface Quick Review Pros Change management Deployments Failure isolation Service Scalability Cons Speed to market Better quality Poor nw performance Monitoring is a challenge Data management Security management Building Microservices Applications Adopting Building Microservices 1 What is needed for MSA 2 Building a business case 3 Brownfield Vs Greenfield MS projects wwwACloudFancom Adoption of MSA Acquire resources with new IT skills Invest in technology eg Cloud Containers Change in culture eg Faster decisions Change in processes eg DevOps Commitment from Business IT Leaders wwwACloudFancom Guide Educate the Business IT teams IT Leader Role of an Architect Business Case for MSA adoption specific to your organization wwwACloudFancom Think Business Think of Business impact not Technology New revenue streams Competitive advantage Customer Loyalty Customer Experience Leverage opportunity Lowered Costs wwwACloudFancom Messaging examples With Microservices architecture we can release our software every 6 weeks rather than every 3 months like we do today IT can help business cut down the product development process to 6 weeks which is 50 faster than our competitor wwwACloudFancom Messaging examples Our monolith apps are difficult to change hence adopting new digital technologies has been slow We need to invest in MSA technologies to be able to move faster Adoption of new digital technologies can help the business achieve the goal of increasing the Lifetime Value of our customer as MSA provides a foundation for faster adoption of these new digital technologies wwwACloudFancom Business Case Doesnt have to be a 50 pages long formal document 5 to 7 slides are fine too J wwwACloudFancom Business Case Clearly layout the Business value quantify Have a roadmap Do a PoC to prove the value Describe what you need to be successful wwwACloudFancom Microservices or Not Think of Business impact not Technology IT Leader What would be the benefit of MSA to my organizations business wwwACloudFancom Microservices projects There are two types of Microservices projects Brownfield Refactor the existing monolithic app Greenfield New application to be built ground up Domain boundaries are somewhat known Domain boundaries are NOT known wwwACloudFancom Monolith to MSA Brownfield Dealing with legacy technologies IT debt Convert application to MSA Refactor Replace Build a new app ground up Big bang Incremental Evolutionary wwwACloudFancom Greenfield Options to build MSA Greenfield Ground up Availability of technology tools Organizations readiness eg DevOps practices processes wwwACloudFancom Greenfield Options to build MSA Greenfield Ground up Monolith First Build a welldesigned monolith app After some experience peel off parts to create MS httpsmartinfowlercomblikiMonolithFirsthtml Quick Review Microservices Project Specific Business benefit to your organization Brownfield Greenfield