4 Years ago, we released this pixel art prototype on Itch because so many strategy games were about growing civilization.
Tomorrow, Terra Nil will be on Nintendo Switch and it has helped us donate over $100,000 to @TheEWT towards real world conservation efforts.
Time to start our xmas #Magento meetup! You can join the live stream at https://t.co/5UzioPl4Kk thanks to amazing @hyva_io and ask questions at https://t.co/oMNuDsbjBE
After last week's release of @ReactPHP MySQL v0.6.0, we immediately started working on a v0.7.x which will contain our upcoming connection pool. 🚀
First changes are already prepared and will go live in the upcoming days. Stay tuned!
https://t.co/PcOsQFu5K9
What's the Business Case for A11Y?
Accessibility is a complex topic! That's why we partnered up with the A11Y experts Snowdog (@SnowdogApps) to assist us!
Read the 1st out of 3 articles on A11Y published on our blog, written by Anna Karoń (@anqa_ka).
https://t.co/icSczpDgG4
@PlaySnowRunner Amy workaround for vehicle discovery event not being fired? I have completed a map but it denies me 100% completion due to 5/8 vehicles discovered when I have them all. Quick Google yielded only "known bug" but no solutions #PS5
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.
#CaseStudy | Social Native's Marketplace
We're proud to share our newest case study!
Earlier this year, we built a full-featured creator marketplace for @socialnative using the @commercetools platform with the MACH approach.
Learn more: https://t.co/nMXUkRogFn
#BlogPost | ReactPHP & MongoDB - Possible Use Scenarios 🛠️
In his latest blog post, our Head of Backend, Kamil Balwierz @mamut144, has been exploring the powerful combination of MongoDB and ReactPHP.
Don't miss out on this insightful read! 👉https://t.co/iKelrvYrna
#BlogPost | ReactPHP & MongoDB - Possible Use Scenarios 🛠️
In his latest blog post, our Head of Backend, Kamil Balwierz @mamut144, has been exploring the powerful combination of MongoDB and ReactPHP.
Don't miss out on this insightful read! 👉https://t.co/iKelrvYrna
@aschmelyun@another_clue I love that thing, but recognize it's limitations. It shines when working with HTTP based backends. So far done few light frontends based on SaaS APIs (plugged in Twig for templating responses). Now having fun using @restheart_org to have there easy access to MongoDb via HTTP
Curious to learn more about the #Hyvä#Magewire#Checkout? @avstudnitz shared his impressions from a developer's point of view at our last #Magento#Stammtisch in #Stuttgart. Check out the recording of his session now! https://t.co/5JS409yACh