2.8 KiB
Refactoring
-
when to refactor
- long method
- too many parameters
- duplicated code
- large class
- too many if else or case when
- temporary variable
- coupling
Microservice
-
benefits
- Each application is relatively small
- Easy to scale
- Improved fault isolation
- One service fails won’t influence others
- You can use different stack for each service
- Each service can be deployed independently
-
drawbacks
- Increased memory consumption
- Developers must deal with extra complexity of creating a distributed system
- Deployment complexity
- To deploy different types of services
OOP
-
Polymorphism
- Code to interface, not an implementation
-
Composition over inheritance
- objects have high cohesion and low coupling with other objects
-
Duck typing
-
SOLID
- Single responsibility
- Open/Closed
- Liskov substitution
- Interface segregation
- Dependency inversion
Functional programming
-
pure functions
- giving a same input, always return same output
- produce no side effects
- reply on no external mutable state
-
function composition
-
avoid share state
-
avoid mutating state
-
avoid side effects
Serverless
-
Lambda
- A lambda is just an anonymous function - a function defined with no name
Closure
- a function value that references variables from outside its body
- In Javascript, not all anonymous function are lamdba, and vise verse
Event Sourcing
Kafka
Apache Kafka is a distributed streaming platform
There are 4 core APIs in kafka:
- Producer API
- Consumer API
- Streams API
- Connector API
Command Query Responsibility Segregation (CQRS)
Every changes you made to the system is a event, events are been persisted and can be replayed to generate the materialized view.
In his book "Object Oriented Software Construction," Betrand Meyer introduced the term "Command Query Separation" to describe the principle that an object's methods should be either commands or queries. A query returns data and does not alter the state of the object; a command changes the state of an object but does not return any data. The benefit is that you have a better understanding what does, and what does not, change the state in your system.
More:
UML
- many_to_many
- one to many
Java Design pattern
Some tips
-
concurrency vs parallelism
- parallelism
- doing a lot of things at once
- about exection
- concurrency
- dealing with lots of things at once
- about structure
- parallelism