Skip to content

Latest commit

 

History

History
84 lines (61 loc) · 2.34 KB

8-organizing-code.md

File metadata and controls

84 lines (61 loc) · 2.34 KB

Become an Architect - 8 - Organizing Code

  • Title: Become an Architect - 8 - Organizing Code
  • Video File Name: Become an Architect - 8 - Organizing Code
  • Preview Video TimeLines: NOT NEEDED

Video Editing Guidelines

  • VIDEO EDITING:
    • 14:00 to about 18:00 - I had a powercut - Please make Siva's reply the starting point to my question to Siva.
  • Thumbnail:NOT NEEDED
  • Video Title: Become an Architect - 8 - Organizing Code
  • TOC
    • Organizing Code
      • What? Why? How?
      • Methods, Classes, Packages and Layers
      • Components and Microservices
      • Best Practices

Image Overlays

None

Text Overlays

None

YouTube Video Description

Become an Architect - 8 - Organizing Code

You can checkout Koushik's Podcast - The Artifact at https://theartifact.io

Koushik (https://javabrains.io/), Siva (https://www.sivalabs.in/) and Ranga discuss Organizing Code.

Entire Series of Videos - https://www.youtube.com/playlist?list=PLBBog2r6uMCS0FX6Ym_8NYeTNykUF5970

Earlier Discussions - https://www.youtube.com/watch?v=WSjaBnOWQ40&list=PLBBog2r6uMCQik02JO_68gqwZbqCrxdRZ

▬▬▬▬▬▬ Chapters ▬▬▬▬▬▬ 
00:00:00 Introduction
00:01:03 Why Organizing Code is important?
00:07:16 Overview of Methods, Classes, Packages and Layers
00:13:53 Package by Layer vs Package by Feature
00:22:59 Functional Programming Principles
00:32:28 Evolution of Orthogonal Architecture
00:42:53 How to choose Architecture style?
00:52:44 Cross-Cutting Concerns

#javabrains #in28minutes #organizing #code #java #architect

Social Media Posts

Time for another exciting discussion.

We discuss how to organize your code with Koushik and Siva.

Here's the complete discussion - https://youtu.be/USZSIN0eBpQ

#javabrains #in28minutes #organizing #code #java #architect

Script

- Organizing Code - Why is it important?
- What are the options?
	- Decision Levels: Method, Class, Package, Layer, Component, Microservice
		- Package by Layer vs Package by Feature
- What principles do you consider?
	- SRP
	- Encapsulation
	- Coupling
	- Cohesion
- Cross-Cutting Concerns: Authentication, Authorization, Logging, Tracing..
- Orthogonal Architecture
- Impact of Architecture style: Microservices, Monolith, Event-Driven on how we organize code
- Advantages of having the standard structure - Ex: Maven
- Advantages of having smaller components