Java Interview: Difference between revisions

From Chorke Wiki
Jump to navigation Jump to search
No edit summary
Line 37: Line 37:


|}
|}
----
==Terminology==
{|
{|
| valign="top" |
| valign="top" |
; [https://www.xinjianl.com/note/software/software-architecture/design-pattern/ Composition vs Aggregation]
; [https://www.xinjianl.com/note/software/software-architecture/design-pattern/ Composition vs Aggregation]
: Both are Association
: Both are Association
: '''Composition:''' A "owns" B
# '''Composition:''' A "owns" B
: '''Aggregation:''' A "uses" B
# '''Aggregation:''' A "uses" B


; [https://www.xinjianl.com/note/software/#:~:text=0x56%20Network Network]
; [https://www.xinjianl.com/note/software/#:~:text=0x56%20Network Network]
: '''Physical Layer:''' Ethernet, 802.11
# '''Physical Layer:''' Ethernet, 802.11
: '''Data Link Layer:''' MAC, ARP, PPP
# '''Data Link Layer:''' MAC, ARP, PPP
: '''Network Layer:''' IPv4, IPv6
# '''Network Layer:''' IPv4, IPv6
: '''Transport Layer'''
# '''Transport Layer'''
: '''Session Layer'''
# '''Session Layer'''
: '''Presentation Layer'''
# '''Presentation Layer'''
: '''Application Layer:''' DNS
# '''Application Layer:''' DNS


| valign="top" |
| valign="top" |


|}
|}
; [https://www.javatpoint.com/devops#:~:text=What%20is%20DevOps? DevOps]
: The DevOps is a combination of two words, one is software '''Development''', and second is '''Operations'''. This allows a single team to handle the entire application lifecycle, from development to testing, deployment, and operations. DevOps helps you to reduce the disconnection between software developers, quality assurance (QA) engineers, and system administrators.
: DevOps tools such as Git, Ansible, Docker, Puppet, Jenkins, Chef, Nagios, and Kubernetes.
# Automation
# Collaboration
# Integration
# Configuration


==References==
==References==

Revision as of 17:20, 24 October 2020

  1. MVC
    1. Model
    2. View
    3. Controller
  2. SOLID Design Principles
    1. Single Responsibility Principle
    2. Open-Closed Principle
    3. Liskov Substitution Principle
    4. Interface Segregation Principle
    5. Dependency Inversion Principle
  1. Design Pattern
    1. Creational Design Patterns
      1. Factory Pattern
      2. Prototype Pattern
      3. Builder Pattern
      4. Singletons
    2. Structural Design Patterns
      1. Adapter Pattern
      2. Composite Pattern
      3. Decorator Pattern
    3. Behavioral Design Patterns
      1. Strategy Pattern
      2. State Pattern
  1. STUPID Practices in Programming
    1. S for Singleton
    2. T for Tight Coupling
    3. U for Untestability
    4. P for Premature Optimization
    5. I for Indescriptive Naming
    6. D for Duplication

Terminology

Composition vs Aggregation
Both are Association
  1. Composition: A "owns" B
  2. Aggregation: A "uses" B
Network
  1. Physical Layer: Ethernet, 802.11
  2. Data Link Layer: MAC, ARP, PPP
  3. Network Layer: IPv4, IPv6
  4. Transport Layer
  5. Session Layer
  6. Presentation Layer
  7. Application Layer: DNS
DevOps
The DevOps is a combination of two words, one is software Development, and second is Operations. This allows a single team to handle the entire application lifecycle, from development to testing, deployment, and operations. DevOps helps you to reduce the disconnection between software developers, quality assurance (QA) engineers, and system administrators.
DevOps tools such as Git, Ansible, Docker, Puppet, Jenkins, Chef, Nagios, and Kubernetes.
  1. Automation
  2. Collaboration
  3. Integration
  4. Configuration


References

Retrieved from "https://cdn.chorke.org/weke/index.php?title=Java_Interview&oldid=3844"