stop overengineering.. just use a database databases can handle auth, queues, drivers, caching, sessions, and more keep it simple 🤌🏻

100%! Everything but queues though imo -- until we get a Horizon DB driver of course. Need that auto-balancing and its child process management. Otherwise its not the greatest experience to have to manually init queue worker daemons for each queue you have

This is very important because many people think they are creating the next Amazon, Netflix, Facebook, Instagram, etc. But only a well-configured database will do the job.

agree

Just use the freaking database

fr

Right up until you have 100 concurrent sessions and need to rearchitect a running prod

Please use MongoDB as database, cause moat data in web applications are nested structures and not excel tables.

W/e just use Laravel and a database xd

Horizon for db driver would help that story.

Would be cool if Horizon were compatible with database driver.

But...Laravel sets up cookies for auth, and changing to Redis for caching is like...5 seconds of work. I think this setup is just a much better starting point for anything.

Why use database as a cache? Isn’t that the same as not caching. I agree with your take, just don’t start caching until you need to.

no; it’s not the same.. imagine an expensive http calls and expensive fetches that can be avoided with a direct fast db call

So what you’re saying is .. I should use the database?

correct

dbs handle the basics right. overengineering kills velocity

Keep it simple, agreed! I usually put Redis in front of the DB though. Still simple.

right / my take is just 99,67 of the projects don’t even need redis.. db just works for caching

@carlmathisen And most of th3 0.33% only need, cause they have clue about software design

@carlmathisen ouch 🌶️