Title: Theory / Unimportant / CS / Programming / Microservice
Tags: récupéré hasSeenConjDef

Name: Microservice
Definition: small (can be rewritten in 2 weeks)
Page: 16
Chapter: 1
Section: What Are Microservices?
Definition2: autonomous
Conjdef: A service
Definition3: working with other such services

Name: Single responsibility Principle
Definition: Gather together those things that change for the same reason, and separate those things that change for different reasons.
Page: 17
Chapter: 1
Section: Small, and Focused on Doing One Thing Wel

Name: Platform as a service
Page: 18
Chapter: 1
Section: Autonomous
Abbreviation: PAAS

Question: How microservices communicate ?
Answer: By network call
Page: 18
Chapter: 1
Section: Autonomous

Name: Application programming interface
Page: 18
Chapter: 1
Section: Autonomous
Abbreviation: API

Name: Coupling
Definition: Entangling system so that one can not be changed without changing the other
Page: 18
Chapter: 1
Section: Autonomous
Context: microservice
Example: Having a system expecting the other to be written in a precise programming language

Name: Technology Heterogeneity
Definition: The fact that different technology may be more suitable for different purposes
Page: 20
Chapter: 1
Example: Saving interaction using graph-oriented database, and post using document-oriented database

Name: Resilience
Definition: The fact that, if a part of a system fail, the remaining doesn't fail.
Page: 22
Chapter: 1

Name: Scaling
Definition: Augmenting the number of computer used for some service when the use of this service increase
Page: 23
Chapter: 1

Question: What are the advantages of microservices
Answer: Allow technology heterogeneity
Page: 20-27
Chapter: 1
Answer2: services are independant, and thus more resilient
Answer3: Scaling can be restricted to the part which actually need it
Answer4: Easier to deploy, since only a small part need to be deploied when a change is done
Answer5: Allow for smaller team, each on a service
Answer6: Composability
Answer7: Allow for lower cost of replacement, part by part

Name: Composability
Definition: The fact that a system may be used in a lot of different way.
Page: 20-27
Chapter: 1
Example: Same system for desktop, tablet, smartphone.

Name: Replaceability
Definition: The fact that a system may be replaced easily by another one
Page: 20-27
Chapter: 1
Context: Microservice

Name: Service-Oriented Architecture
Definition: a design approach where multiple services collaborate to provide some end set of capabilities.
Page: 28
Chapter: 1
Section: What About Service-Oriented Architecture?
Context: Micro Service
Abbreviation: SOA

Name: Service-Oriented Architecture Protocol
Page: 28
Chapter: 1
Section: What About Service-Oriented Architecture?
Abbreviation: SOAP

Question: Other Decompositional Techniques
Answer: Shared libraries
Page: 30-32
Chapter: 1
Answer2: Modules

Question: Advantage of microservice over libraries
Answer: Library does not allow heterogeneity, since they are usually written for a single language/platform
Page: 30-32
Chapter: 1
Section: Other Decompositional Techniques
Answer2: Harder to scale for a library than for an equivalent service
Answer3: Can't deploy new library without deploying the processes using it