Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Teach me master!
Don't forget to share the link when done, I'd love to see the output of what you described in your rant :D -
@Divisionbyzero Thanks :D
By the way out of scope question, PHP or NodeJs for backend? I usually do C# but now I'm into NodeJs, not sure if I need to learn PHP for backend or what I know is enough -
Wombat102467y@gitpush I use PHP. Node.js was on the list, too. But then I decided it would be an overkill for my needs and choose Laravel. 😅
-
I also have a similar workflow. Difference is that in the Backend I use Koltin with ktor.io and on frontend I use Nuxt which builds on Vue and makes the dev enviroment easier to overlook.
-
tahnik387587y@Divisionbyzero Laravel is way too complicated for something like a portfolio website. With nodejs you could use express which is a lightweight server. It takes a lot less time to build and run the server as well. But whatever you did is awesome too 🙂
-
@Divisionbyzero @tahnik thanks for your input guys.
If I'm not mistaken devRant uses Nodejs for the backend, let us assume it reaches 1million user with 500K online at any given time, will NodeJs be able to handle that load, or going with PHP, C#, Java would be a better choice? -
@gitpush
Here is an article about scaling NodeJS and it recommends Microservices for 100k to 999k concurrent users. http://adrianmejia.com/blog/2016/... -
tahnik387587y@gitpush If I ever had that many users with that many requests, I would create server in either C++ or Go.
You could continue to use nodejs with something like kubernetes. -
Wombat102467y@tahnik good point, though I had to learn node.js installation and serving first. PHP and Apache I knew pretty well, so for me Laravel is okay. I always had the which to learn both so it was just a decision about "wich is faster to do in the current situation". 😅
Related Rants
Last night I nearly finished my portfolio site. I was working on the perfect framework and workflow like forever. But in the end I accomplished a pretty pleasing solutions. For the back-end I choose Laravel with it's built in rest-api, the front-end is managed by Vue. I'm also proud of my assets-management which is handled by Gulp + Webpack (Laravel Mix). But here I decided to run Gulp on images, fonts and CSS and let Webpack bundle the JavaScript.
And what really crawls my balls is that I can write Sass and Jade, even use partials and organized the shit out of this website, and let Gulp just vomit some minified HTML and CSS on the other end.
Man that feels so good.
rant
devgasm
javascript
sass
webpack
css
laravel
vue
jade
html
gulp
workflow