Aurelia

Backend Software Engineer from Singapore
#golang #Laravel

[Aurelia @loribeanl]

Chills!! It’s a classic book for a reason 💀 #cleanarchitecture

[The Go Dev @TheGoDev]

Implementing JWT Authentication in a Golang Application

Authentication in Go? I'd better JWT this down.

{ author: @eaytin } #DEVCommunity #GoLang
https://t.co/O5FXLYAZax

[Matt Boyle @MattJamesBoyle]

This one is a bit more of a mini-tutorial than my other #golang tips and was very popular. Some great further discussion in the comments too.

Now available on https://t.co/oWZs2sn5s0

[Aurelia @loribeanl]

Diving deeper into #golang, I stumbled upon the surprising nuances of nil 🤯. It tripped me up for a bit, so here's a quick tip that might help someone else! #golangtips

[Aurelia @loribeanl]

Just wrote my first-ever article! To-do apps become surprisingly complex when you add in recurring tasks/schedules 😂 https://t.co/eOZFCNquIG
#systemsdesign #database

[Rakesh Jain @devops_tech]

Mastering Docker File 🐳

A thread explaining everything about a Docker File 👇

[Aurelia @loribeanl]

🙌 Made my first open-source contribution to the #Laravel Adjacency List package! 🚀 The enhancement adds support for customized precision & scale for decimal columns, preventing SQL errors. Grateful for the opportunity to contribute! https://t.co/r5Q7LkVfXn

[Backpack for Laravel @laravelbackpack]

#Laravel Tip: Simplify eager loading with Laravel's withDefault() method. 🔍 Load relationships and provide default values if the related model does not exist.

[Elad Gasner 🇮🇱 @GasnerElad]

#Laravel Tip: 💡 Cool vs. Useful! 😎 While the ?? operator is cool, the data_get helper in @laravelphp is more useful. 🚀 Simplify null value handling and access complex data structures effortlessly. Boost code efficiency with data_get!

[Ruan Bekker 🇿🇦 @ruanbekker]

Great repository with packed #devops content! 🥳

#gitops #terraform #kubernetes https://t.co/KwPEsqNtXx

[Anis Ahmad @ajaxray]

In #Laravel, if you want to have an artisan command to create some users manually, you can just copy-paste this gist:

https://t.co/jMWX42GeuB

[Bilgin Ibryam @bibryam]

Error Handling in Event-Driven Systems
https://t.co/zieHgJd4mc

[Taylor Otwell @taylorotwell]

Laravel Precognition is ready to predict the future! 🧠

Easily add real-time validation to your JS + Inertia powered Laravel apps without duplicating your validation logic on the front-end.

If you're using Livewire this is already easy for you. 😛

https://t.co/QSa2RT7bsq

[Taylor Otwell @taylorotwell]

One of my Laravel ✨ best practices ✨ is only using the 7 "restful" methods in my controllers.

Controllers only have: index, show, create, store, edit, update, delete.

Think you need another method? You really need another controller. Built *all* of Vapor like this.

[Christoph Rumpel 🤠 @christophrumpel]

Do you know what this PHP code does? 🤔

[Eric Scott @ercsctt]

Starting a new Laravel project? Add this to your AppServiceProvider. Your future self will thank you 😅

✨ No lazy loading
🚫 Exceptions when assigning non-fillable attributes
👻 Prevents accessing attributes that weren't retrieved or didn't exist

[Trevor Gehman @trevorgehman]

In #Laravel I often need to get the number of distinct values of a column, along with a count. Here's a quick way to do that on any model:

[Aurimas Griciūnas @Aurimas_Gr]

Some thoughts on 𝗥𝗲𝗮𝗱𝗶𝗻𝗴 𝗗𝗮𝘁𝗮 from 𝗞𝗮𝗳𝗸𝗮.

Kafka is an extremely important 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗱 𝗠𝗲𝘀𝘀𝗮𝗴𝗶𝗻𝗴 𝗦𝘆𝘀𝘁𝗲𝗺 to understand, last time we covered Writing Data.

𝗦𝗼𝗺𝗲 𝗿𝗲𝗳𝗿𝗲𝘀𝗵𝗲𝗿𝘀:

➡️ Clients writing to Kafka are called 𝗣𝗿𝗼𝗱𝘂𝗰𝗲𝗿𝘀.
➡️ Clients reading the Data are called 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿𝘀.
➡️ Data is written into 𝗧𝗼𝗽𝗶𝗰𝘀 that can be compared to tables in Databases.
➡️ Messages sent to 𝗧𝗼𝗽𝗶𝗰𝘀 are called 𝗥𝗲𝗰𝗼𝗿𝗱𝘀.
➡️ 𝗧𝗼𝗽𝗶𝗰𝘀 are composed of 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻𝘀.
➡️ Each 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻 is a combination of and behaves as a write ahead log.
➡️ Data is written to the end of the 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻.
➡️ Each 𝗥𝗲𝗰𝗼𝗿𝗱 has an 𝗢𝗳𝗳𝘀𝗲𝘁 assigned to it which denotes its order in the 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻.
➡️ 𝗢𝗳𝗳𝘀𝗲𝘁𝘀 start at 0 and increment by 1 sequentially.

𝗥𝗲𝗮𝗱𝗶𝗻𝗴 𝗗𝗮𝘁𝗮:

➡️ Data is read sequentially per partition.
➡️ 𝗜𝗻𝗶𝘁𝗶𝗮𝗹 𝗥𝗲𝗮𝗱 𝗣𝗼𝘀𝗶𝘁𝗶𝗼𝗻 can be set either to earliest or latest.
➡️ Earliest position initiates the consumer at offset 0 or the earliest available due to retention rules of the 𝗧𝗼𝗽𝗶𝗰 (more about this in later episodes).
➡️ Latest position initiates the consumer at the end of a 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻 - no 𝗥𝗲𝗰𝗼𝗿𝗱𝘀 will be read initially and the 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 will wait for new data to be written.
➡️ You could codify your consumers independently, but almost always the preferred way is to use 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽𝘀.

𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽𝘀:

➡️ 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽 is a logical collection of clients that read a 𝗞𝗮𝗳𝗸𝗮 𝗧𝗼𝗽𝗶𝗰 and share the state.
➡️ Groups of consumers are identified by the 𝗴𝗿𝗼𝘂𝗽_𝗶𝗱 parameter.
➡️ 𝗦𝘁𝗮𝘁𝗲 is defined by the offsets that every 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻 𝗶𝗻 𝘁𝗵𝗲 𝗧𝗼𝗽𝗶𝗰 is being consumed at.
➡️ 𝗦𝘁𝗮𝘁𝗲 of 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽𝘀 is written by the 𝗕𝗿𝗼𝗸𝗲𝗿 (more about this in later episodes) to an internal 𝗞𝗮𝗳𝗸𝗮 𝗧𝗼𝗽𝗶𝗰 named __𝗰𝗼𝗻𝘀𝘂𝗺𝗲𝗿_𝗼𝗳𝗳𝘀𝗲𝘁𝘀.
➡️ There can be multiple 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽𝘀 reading the same 𝗞𝗮𝗳𝗸��� 𝗧𝗼𝗽𝗶𝗰 having their own independent 𝗦𝘁𝗮𝘁𝗲𝘀.
➡️ Only one 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 per 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽 can be reading a 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻 at a single point in time.

𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽 𝗧𝗶𝗽𝘀:

❗️ If you have a prime number of 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻𝘀 in the 𝗧𝗼𝗽𝗶𝗰 - you will always have at least one 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 per 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽 consuming less 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻𝘀 than others unless number of 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿𝘀 equals number of 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻𝘀.

✅ If you want an odd number of 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻𝘀 - set it to a 𝗺𝘂𝗹𝘁𝗶𝗽𝗹𝗲 𝗼𝗳 𝗣𝗿𝗶𝗺𝗲 𝗡𝘂𝗺𝗯𝗲𝗿.

❗️ If you have more 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿𝘀 in the 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽 then there are 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻𝘀 in the 𝗧𝗼𝗽𝗶𝗰 - some of the 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿𝘀 will be 𝗜𝗱𝗹𝗲.

✅ Make your 𝗧𝗼𝗽𝗶𝗰𝘀 large enough or have less 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿𝘀 per 𝗖𝗼𝗻𝘀𝘂𝗺𝗲𝗿 𝗚𝗿𝗼𝘂𝗽.

--------

Follow me to upskill in #MLOps, #MachineLearning, #DataEngineering, #DataScience and overall #Data space.

Also hit 🔔to stay notified about new content.
𝗗𝗼𝗻’𝘁 𝗳𝗼𝗿𝗴𝗲𝘁 𝘁𝗼 𝗹𝗶𝗸𝗲 💙, 𝘀𝗵𝗮𝗿𝗲 𝗮𝗻𝗱 𝗰𝗼𝗺𝗺𝗲𝗻𝘁!

Join a growing community of Data Professionals by subscribing to my 𝗡𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿.

[Milan Jovanović @mjovanovictech]

I have used the CQRS pattern on a few different projects now.

Here's what I think about it.

Pros of CQRS:
- Single responsibility - Commands / Queries
- Decoupling
- Flexibility - Single DB, separate read/write DB, event sourcing
- Testability

Cons of CQRS:
- Complexity
- Learning curve
- Harder to debug
- Many smaller components

I want to share a few more observations.

New people on the project become productive very quickly

CQRS is about logically splitting reads and writes.

You learn to treat reads and writes differently and optimize each use case.

P.S. If you like actionable tips on .NET, consider joining my newsletter.

I write an email to 14,000+ engineers every Saturday that helps you learn software architecture and the latest .NET trends, all in 5 minutes or less.

Subscribe here: https://t.co/M6og1UeWzm

Have you used the CQRS pattern?

[Tobias_Petry.sql @tobias_petry]

⚡ Database Tip

Recursive queries are a great solution to e.g. querying multiple levels in a tree with just one query. But you should use cycle detection otherwise your query might run forever or fail for loops in your data.

https://t.co/DaAVDMLv1N