Gopher Academy

✅ پادکست وبینار مهندسین گولنگ پارسی

دوستان از طریق Spotify و Google Podcasts و همچنین castbox می توانید وبینار را گوش دهید.

در این وبینار درخصوص جامعه برنامه نویسان ایران و همچنین در خصوص بازار کار و درآمد استک گو در داخل یا خارج پرداختیم و تجربیان خیلی خوبی مطرح شد برای اینکه بتوانید یک فرصت شغلی مناسبی بدست آورد.

🔗 https://open.spotify.com/show/6aQdgKiOF5tuzI7mpijlfj

🔗 https://podcasts.google.com/feed/aHR0cHM6Ly9hbmNob3IuZm0vcy9kZGY3OWRiNC9wb2RjYXN0L3Jzcw

🔗 https://castbox.fm/va/5381928

➖➖➖➖➖➖➖➖➖
🔰@gopher_academy

🐳3💊2🕊1

828 viewsJavad, edited 19:03

Gopher Academy

Why do we need message brokers 👇?

Message brokers play a crucial role when building distributed systems or microservices to improve their performance, scalability, and maintainability.

🔹 Decoupling: Message brokers promote independent development, deployment, and scaling by creating a separation between software components. The result is easier maintenance and troubleshooting.
🔹 Asynchronous communication: A message broker allows components to communicate without waiting for responses, making the system more efficient and enabling effective load balancing.
🔹 Message brokers ensure that messages are not lost during component failures by providing buffering and message persistence.
🔹 Scalability: Message brokers can manage a high volume of messages, allowing your system to scale horizontally by adding more instances of the message broker as needed.
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

❤2👍1🤔1🐳1

679 viewsBardia, 03:30

Gopher Academy

1681130553260.pdf

2.6 MB

Does #Kubernetes rebalance your Pods?
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

👍4

878 viewsBardia, 07:30

Gopher Academy

اگر دنبال یه کلاینت رایگان، اپن سورس و سبک برای دیتابیس های SQL و NoSQL هستید حتما DBGate رو امتحان کنید.

برای لینوکس، ویندوز، مک و مرورگر های وب هم قابل استفاده س.

https://dbgate.org/
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

👍4

681 viewsBardia, 11:30

Gopher Academy

POCO vs DTO vs Entity vs VO

POCO, DTO, Entity and VO are programming concepts used in software development. A better understanding of where we use them might help us make better code:

POCO (Plain Old CLR Object)
▪️ POCO classes hold data and represent business models.
▪️ POCO classes do not have any behavior.
▪️ They are used to persist data.
▪️ POCO classes are not framework-dependent.
▪️ hey should not contain any validation or persistence rules.

Data Transfer Object (DTO)
▪️ A DTO transfers data between layers, processes, or applications.
▪️ A DTO is immutable and has no behavior.
▪️ A DTO is optimized for serialization and deserialization for efficient data transfer.
▪️ A DTO only represents data and should not have business logic or validation methods.
▪️ Data transported by a DTO may not be reliable from a business perspective.
▪️ A DTO represents data needed by the consumer, not business entities directly.
▪️ A DTO should include only relevant data from one or multiple sources for a specific purpose.

Entity
▪️ Entities encapsulate business models related to database tables or domain units.
▪️ Entities validate, CRUD, fetch related data and apply business logic in a domain layer.
▪️ Validated entity changes allow persistence and visibility for consistency across layers.
▪️ Entities can represent non-table domain objects and are used in frameworks for mapping tables.

Value Object (VO)
▪️ VOs are immutable objects holding valid data for independent entities like dates or monetary amounts.
▪️ VOs shouldn't be used for persistence, but can represent properties of domain objects in a database.
▪️ Comparing VOs should consider property values, not references for equivalent object treatment.
▪️ VOs ensure valid data and provide necessary info to consumers via constructors, static factory methods or builder patterns.

➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

👍5❤1🤔1🐳1

888 viewsBardia, 15:30

Gopher Academy