π Hey!
I share how I'm creating #microSaaS π§π½βπ» and growing them to $15k MRR π―, bootstrapping #eCommerce in πΊπ¦, and enjoying life πΎπ.
Startup landing page in @framer π
I'm giving it away for FREE! (really)
Comment "Framer" below and I'll send it to you π
(must be following so I can DM)
Working with numerous time zones is always challenging and creates significant cognitive load. A desktop widget, inspired by Dieter Rams' principles, featuring intuitive functionality and a sleek visual design, would be an excellent solution.
Today's Laravel release brings new "Number" helper methods, including methods to easily format monetary values, file sizes, and more.
Read more in the docs: https://t.co/Nz7xYjp1qF
I overhauled the @supernotesapp website navigation this week π₯
Often, nav menus are just directories β boring and static. This new take communicates our values and shows live sneak peeks of each section, pulling from our pages & RSS feeds #UI #UX#Update
A Belarusian bear has had enough of Lukashenko, the Wagner Group and Russian domination of his country.
He decided to investigate whether itβs possible to cross the border fence with Lithuania and seek freedom in the EU.
π±πΉ
For many years, I considered all talk about scale to be irrelevant. If you throw enough money at it, any web stack can scale to handle more traffic.
With an abundance of free investor money, I've always believed that startups should choose the stack that allows them to move faster and further.
As focus shifted to profitability in the recent year or two, cost control has become an important concern.
PHP is my favorite programming language, but it blocks execution threads and network connections (DB, HTTP, Cache, etc.). Should we abandon PHP? NO! is my answer! Why should development speed be sacrificed for cost control? Why not have it both ways?
I placed a bet on PHP and added GoLang to the stack and the results exceeded my expectations.
Here's a look at my current stack (for cost control):
1. All web clients talk to a load balancer.
2. The load balancer handles SSL & routes most requests to the PHP monolith.
3. Requests to endpoints that receive high traffic & perform many I/O operations are routed to a Go web server.
4. The PHP monolith & Go server dispatch tasks to the queue & read/write from/to database & cache clusters.
5. A separate Go program handles background jobs (from the queue) and periodic tasks (scheduled).
What do I get from Go?
- Handlers waiting for I/O operations yield to the runtime so others can run.
- I can handle concurrent workloads without having to start new worker processes. Which translates to less memory consumption.
- Network connections are kept alive & re-used.
- Database connections are put back for reuse once the query finishes. They aren't kept hostage until a response is sent.
What do I get by keeping PHP?
The tooling available in the ecosystem (& Laravel in specific) is lightyears ahead. It allows developers to get things done faster by spending their time adding functionality rather than re-inventing the wheel.
Should you switch to this stack?
Are you struggling with compute infrastructure cost at the moment? If the answer is no, stick with PHP. It'll help you move faster, add value, onboard more customers, and hopefully get crazy traffic so you start having infrastructure cost concerns :) That's a nice problem to have, specially that solutions are available.