Dano Seto Anbela

slowresp

[Anies Rasyid Baswedan @aniesbaswedan]

Izinkan ikut berpendapat tentang situasi belakangan ini…

[Dano Seto Anbela @otesotes]

@suryanaaa29 @ayooowhatsupmen @swansage11 Dari dia lebih milih judol ketimbang fokus grinding aja udh aneh bang 🤣

[Dano Seto Anbela @otesotes]

@UnitedCoreID @VrxXaferusr @idextratime Eh iya modric, ngapa jadi mudric. Thankyou koreksinya bang wkwk

[Dano Seto Anbela @otesotes]

@VrxXaferusr @idextratime Itu namanya Black Magic bro. Dulu pernah kan menang lawan siapa tapi shoot on targetnya 0 wkwk. Emang gamau berkembang ini tim. Udh capek dukungnya, musim ini aja ketolong mudric. Gatau dah kalau mudric pensiun/keluar gimana nasibnya wkwk

[Dano Seto Anbela @otesotes]

@qrivasiii Nih min lanjutannya

[Dano Seto Anbela @otesotes]

@GeneralSonCast Ngeliat komen di ig rrq, yang nge hate pada di serang fans beliau 🤣

[Dano Seto Anbela @otesotes]

@dakdan98 @GeneralSonCast kayaknya ini bigmo jadi ba rrq

[Elon Musk @elonmusk]

Banger 😂

[Dano Seto Anbela @otesotes]

Cobaannya beneran ga main main ya ternyata 😔

[Dano Seto Anbela @otesotes]

@reyfearless @TxtdariHI Wkwkw dari jaman covid emang gapernah belajar.

Negara lain udh pada lockdown dan nutup penerbangan dari luar, eh kita malah sebaliknya 🤣.

Gabisa apa ya mereka ga nunggu parah dulu baru gerak tapi antisipasi sebelum itu menjadi parah

[Dano Seto Anbela @otesotes]

@hisanaburger @LambeSahamjja Kemarin Iran udh kasih 4 point buat mereka berhenti kirim rudal ke Israel. Salah satunya jangan pernah ganggu Iran lagi sama Amerika harus bener-bener cabut dari negara-negara Teluk. Dari 2 point ini aja agak sulit wkwk

[Dano Seto Anbela @otesotes]

@meaninggoy @bakuldimsum_ Elon musk ngikutin keknya 😂

[Dano Seto Anbela @otesotes]

@allfromme_ @KucengTerbanggg Si nyamuk nyedot spidol, dia ngira merah itu darah

[yourclouddude @yourclouddude]

AWS ARCHITECTURE explained 👇

[Dhanian 🗯️ @e_opore]

Clean Architecture

→ Clean Architecture is a software design approach that separates business logic from frameworks, databases, and external tools.
→ The core idea is independence — your application logic should not depend on UI, databases, or third-party services.
→ Dependencies always point inward, toward the business rules.
Analogy: A Castle with Protected Inner Chambers
→ Imagine a castle:
→ The inner chamber holds the king and royal secrets (core business logic).
→ The outer walls protect the castle and handle interactions with the outside world (UI, APIs, databases).
→ You can replace the gates or walls without touching the royal chamber.

That is how Clean Architecture protects your application core.

Architecture Layers (Outside → Inside)

→ Frameworks & Drivers Layer (Castle Walls)
→ Includes UI frameworks, databases, web servers, external APIs.
→ Examples: React, Spring Boot, Express, PostgreSQL.
→ Handles communication with the outside world.
→ Interface Adapters Layer (Guards & Translators)
→ Converts data between external formats and internal formats.
→ Contains controllers, presenters, gateways.
→ Makes sure the outside world can talk to the inner layers safely.

→ Use Cases Layer (Castle Operations Room)

→ Contains application-specific business rules.
→ Coordinates workflows and system behavior.
→ Example: CreateOrder, RegisterUser, ProcessPayment.

→ Entities Layer (Royal Chamber)

→ Holds core business rules and enterprise logic.
→ Completely independent of frameworks and tools.
→ The most stable and reusable part of the system.

Dependency Rule
→ Outer layers → depend on → inner layers
→ Inner layers → never depend on → outer layers
→ Business logic remains protected from technical changes.
Flow

→ User action → UI → Controller → Use Case → Entity
→ Result → Use Case → Presenter → UI
→ Infrastructure supports the flow but never controls it.

Benefits

→ Strong separation of concerns.
→ Highly testable business logic.
→ Easy to swap databases, UI frameworks, or APIs.
→ Long-term maintainability.
→ Encourages clean, scalable codebases.
Drawbacks
→ More abstraction and initial setup.
→ Requires discipline to enforce boundaries.
→ Can feel complex for small projects.

Best Practices

→ Keep business logic framework-independent.
→ Define interfaces in inner layers.
→ Implement details in outer layers.
→ Use dependency injection.
→ Treat tools and frameworks as replaceable plugins.

When to Use
→ Medium to large-scale applications.
→ Systems with complex business rules.
→ Long-term projects requiring maintainability.
→ Teams following domain-driven design principles.
📘 Mastering Software Architectures: From Monoliths to Microservices and Beyond

Learn Clean Architecture, Hexagonal Architecture, Onion Architecture, CQRS, MVC, MVVM, Event-Driven, Microservices, and more — with real-world analogies, diagrams, and best practices to help you design scalable and maintainable systems.

👉 https://t.co/rQ5uqOjO5c

[Dhanian 🗯️ @e_opore]

Docker concepts explained to a 10 year old.

[Skilled Coder @theskilledcoder]

Microservices Patterns Cheatsheet

[Ashish Pratap Singh @ashishps_1]

What is JWT and how it works?

JWT (JSON Web Token) is a compact, URL-safe token used to securely transmit information between a client and a server.

It is most commonly for authentication in modern web apps.

A JWT has three parts separated by dots: xxxxx[dot]yyyyy[dot]zzzzz

1. 𝐇𝐞𝐚𝐝𝐞𝐫: Contains the algorithm used for signing the JWT (e.g., HMAC SHA256 or RSA) and the token type (JWT).
2. 𝐏𝐚𝐲𝐥𝐨𝐚𝐝: Contains the "claims", statements about an entity (typically, the user) and additional data.
3. 𝐒𝐢𝐠𝐧𝐚𝐭𝐮𝐫𝐞: Used to verify that the sender and ensure the token hasn’t been tampered with. Generated by taking the encoded header, the encoded payload, a secret, and the algorithm specified in the header, and signing it.

How does it work?
1. The user logs in with credentials.
2. The server validates credentials and generates a signed JWT.
3. The server sends the JWT back to the client.
4. The client stores the JWT token (typically in localStorage or cookies).
5. For future requests, the client includes the JWT in the Authorization header.

Key Benefits:
- Statelessness: No need to store session information on the server, making APIs more scalable.
- Security: Digitally signed to prevent tampering.
- Compact: Small size allows for efficient transmission.

♻️ Repost to help others in your network

[Dano Seto Anbela @otesotes]

@GeneralSonCast SP1 minimal keluar lah pak GM. Agak deg2an itu game 1

[Alex Xu @alexxubyte]

Behind the Scenes: What Happens When You Enter Google[dot]com