https://laravel.com https://laracasts.com
Why would be interested in any other :P
Are there any “famous” websites built in laravel that someone not in the Laravel world might know?
Like any major retailers? Any major platforms or organisations?
Thanks.
https://laravel.com https://laracasts.com
Why would be interested in any other :P
@jlrdw why don't you try to answer his question correctly instead of just a random statement about something he didn't ask for? You literally answered the opposite of what he asked for...
Anyways.. I'm working for a company in Denmark, we use Laravel, and serves roughly 1000 users a day in our platform In Denmark we're kinda famous
Well I wont say there are many big brand sites that are on Laravel yet, but there are quite a few new brands that are enjoying the Laravel awesomeness. Here are a few good examples to look into
Deltanet Travel.
Neighborhood Lender.
Laravel Tricks.
World Walking.
Mack Hankins.
LaravelIO.
FusionInvoice.
Cachet.
Thanks for all the replies. Don't get me wrong, I understand that this is a bit of an annoying question. Let me explain why I'm asking.
I'm working for a startup just now who have just received some serious (serious!) venture capital funding.
I have built their platforms up to this point in Laravel and our native apps are also hitting Laravel for the API.
I'm wondering WHY there are no really big (in terms if users and platform interactions) organisations using Laravel, as I intend to continue building with Laravel. Am I digging my own grave.
@jlrdw Wow that's some world class, top quality mansplaining going on there. Well done :-)
@jlrdw and as if any of those companies listed had just ONE website !
I guess part of the challenge is that a) established 'major' sites made their architecture decisions a long time ago and b) they are not likely to advertise their architecture and c) their deployments are going to be varied depending on the use case.
(unless you are twitter and all their famous fail-whale issues which told everyone they were a Rails shop)
Perhaps this will help;
https://trends.builtwith.com/websitelist/Laravel
Its interesting to look at some of the 600,000 sites listed.
Going back to my earlier comment, CathayPacific may not use it on their main site, but they probably have a lot of small properties such as their careers site which is using Laravel https://careers.cathaypacific.com/
why isnt PHP good for entreprise systems?
It is fine for small Enterprise just not large Enterprise but you'd really have to go back and study the history and making of PHP.
For example you are not going to find PHP used in a large supply chain like Sam's Walmart systems it just ain't going to do it.
And as far as laravel is concerned, that shouldn't really be applicable to the question rather it should be a technology question, i.e., Who uses what technology and why namely:
Who uses
Etc
Weather laravel or yii2 or cakephp or plain php, it's the technology used not the framework that matters.
But I do like laravel for PHP the best Taylor made it very easy to use and very flexible.
But PHP could be used for large Enterprise but you would need C++ classes compiled for some of the heavy hitting.
I came from java Enterprise I am semi-retired now and PHP and laravel is perfect for the smaller sites I do sometimes.
but I also have a custom framework and I have written and have updated overtime to stay up-to-date with the latest PHP.
Usually a very large company first of all is not going to use any framework usually they have proprietary in house custom code tailored to the exact needs of the company.
That's all folks
More mis-information. 'Enterprise class' websites are not written as huge monoliths anymore - although of course there are a lot of them out there still.
'Enterprise class' websites are not written as huge monoliths anymore
Just take CH Robinson as an example. They have offices all over the U.S. and all over the World. They probably do more database transactions in a week than all on this forum members combined does in a year.
Their software infra structure cost is a good 23 million dollars.
You cannot have that large of a logistics setup without monolith.
Now for more education:
As an example, the State of Texas uses java technology, very business looking in the background for employees.
The part the public sees and uses is not the same, it's prettied with all the bells and stuff, pretty css, JS, etc.
I believe it's Landstar that also uses PHP for some of their stuff. But not the heavy logistics stuff in the background.
So many enterprise will use a vast array of technologies.
And how do you define a
famous site
All sites are famous to their owner, and mean something.
@jlrdw have you personally been involved in a company being built from the ground up, since 2015, or is your experience limited to what these old companies were doing 20 years ago? Have you built a laravel app, using centralized storage, redis, load balancers and multiple app workers? Or have you just built laravel apps that run on a single server?
I am not a server person but I built the software ground up at a trucking company, it was Java but had help with the server stuff.
Worked for State of Tx, was java.
After being semi retired did a Humane Society site for quite a while, it was PHP.
But that was shared hosting.
And mostly just some small projects here and there. Been using laravel since 4.2.
But I knew I.T. Folks at CH Robinson, and out of curiosity I plucked their mind on the kind of software and stuff they used and they went over it with me.
The thing is Java technology has much longer backwards compatibility therefore that's why Enterprise's drawn to it.
The longer backwards compatibility is part of the design spec.
Out of curiosity one day I installed the latest Java EE and sure enough my old code from over 11 years ago still worked.
Of course I realize that if used for real things like the hashing of passwords and security would have to be updated it's not a real app anymore but I was just curious if it would still work.
anyway not everyone uses mix and libraries and packages a lot of people still write custom CSS and their own custom Js.
I tried bootstrap one time it's okay, but if you have a site where many pages uses different custom themes that the customer wants then bootstrap just doesn't make no sense that's where custom CSS comes.
You have to remember any package or library used and even laravel the backbone core is still the basic language, like laravel has a backbone PHP and PDO, no big mystery there.
Some of the neat JavaScript libraries or packages, the guts is still JavaScript.
So I guess I am just used to writing my own CSS and custom media queries, and yes I do use jQuery not plain JavaScript.
But usually use JavaScript sparingly not overuse.
I guess another way of looking at it is sites today the backend code is basically the same has not changed over the years that much, where as front end has kind of come Leaps and Bounds with various beautifications.
But returning basic database results and the basic queries are the same.
TLDR: No, my experience is limited to working with Java many years ago before I semi-retired. Since then I've played around with laravel and php and built a site for the Humane Society on shared hosting, but haven't used it in any significant way and don't know about horizontal scaling.
Fully stocked with popcorn!
Not sure on Laravel, but PHP runs numerous large scale sites. Just look at Wikipedia and Wordpress.com. Large parts of Facebook still run on PHP as well.
whitehouse.gov is now on Wordpress. During Obama's years it was on Drupal. Numerous US government sites still use Drupal.
When you look at Enterprise, it's more common than not to see numerous different languages and frameworks powering the various services that make up their entire online presence.
@jlrdw you only have experience of one language Java with a bit of php/.net (Sorry didnt want to read your big post, just skim read it)..
my last post wasnt a question it was directly aimed at your first post saying php cant be used for entreprise..
and your
you cannot have that large revenue/whatever without a monolithic
are you insane? yes you can - microservices isnt just an inferior thing that wont be handle 1000s transactions - in fact thats the reason why people build microservices so they want to be able to handle 1000 transactions..
Facebook and the BBC website?
BBC was written using a combination of Zend and RoR for many years and they don't come much bigger. They have since migrated to NodeJs using ExpressJs.
I work with micro services and of course you can write an enterprise app without a monolith, that's the point. Netflix is a blue chip micro service solution.
I have a couple friends who worked on a FedEx shipping site a few years ago. It was built using PHP. (They think it still is)
I'm a veteran PHP, Java and C#.Net developer. (I do C# now and did Java for 8 years for my day job) I'd put any of my PHP sites up against any of my Java sites and the performance of PHP would run circles around Java. In my experience, Java requires WAY more resources to run enterprise apps. (I've spent way too many hours into tweaking WebSphere to not bog down and die) Not sure what you worked on in Java, @jirdw but it must have been pretty light.
You also got really lucky running your 11 year old code on modern Java EE. Anything substantial we did would often break with the next EE release which almost always contained breaking changes.
I only worked with JSP, servlets and Beans. The spec from oracles says:
Q: Can applications written for prior versions of Java EE run in a Java EE 6 implementation?
And answer:
Java EE applications that are written to the J2EE 1.3, J2EE 1.4, or Java EE 5 specification will run on a Java EE 6 implementation. Backwards compatibility is a requirement of the specification.
I tested some old code using Java EE 7 that was written using J2EE 1.4, in other words quite a while back.
You are probably right, some of the code, perhaps JSF (Java server faces) code might not work.
I never used JSF, only JSP, servlets and Beans. I think some of the imports changed, like:
import javax.servlet.http.HttpServletRequest;
etc.
But the basics, all worked, like in the servlet: and this is just from a test database I use:
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
pdao.PetDAO petDAO = new pdao.PetDAO();
String t1;
t1 = request.getParameter("t1");
petDAO.sett1(t1);
try {
List<Pet> pets = petDAO.list();
request.setAttribute("pets", pets);
request.getRequestDispatcher("petlist.jsp").forward(request, response);
//above line sends data to view
} catch (SQLException e) {
throw new ServletException("error msg here", e);
}
}
Was all good
But you are right their may be small tweaks here and there.
But I don't mess with java any more.
Someone mentioned netflix, java is used on the backend.
And I already mentioned that many large enterprise will use several technologies, including php. It just depends on where and how.
Oh the php written thing for fedex is an api they have for any language
https://www.easypost.com/fedex-php-api.html
One for java
https://www.easypost.com/fedex-java-api.html
It's just to use the api.
But their software is java, a recent job post
COMPANY: FedEx Services JOB TITLE: Software Developer - Java All Levels JOB REQUISITION NUMBER: RC32010 CATEGORY: General LOCATIONS: Collierville, Tennessee 38017 United States JOB DESCRIPTION: The responsibility of this position is for developing and implementing Enterprise Customer solutions. This position will also have a heavy focus on the development for identifying, matching, and building associations for customer contacts. Duties for this role include but not limited to design, document, code, test, and deploy software to support the software development life cycle. May develop prototypes and solutions using a diverse range of technology. Apply modern principles, methodologies, tools, and systemic processed to support the launch of new business capabilities. KNOWLEDGE/SKILLS CONSIDERED A PLUS: * JAVA/JMS/Spring/SOAP Web Services * Server side background * Oracle, SQL, Data Modelling skills * Analytical/problem solving skills * Master Data Management background * Experience with...
Company: FedEx Services Job Title: Software Developer (All Levels) Job Requisition Number: RC34934 Category: General Locations: Irving, Texas 75063 United States
Duties for this role include but not limited to design, document, code, test, and deploy software to support the software development life cycle. May develop prototypes and solutions using a diverse range of technology. Apply modern principles, methodologies, tools, and systemic processed to support the launch of new business capabilities.
Duties for this role include but not limited to design, document, code, test, and deploy software to support the software development life cycle. May develop prototypes and solutions using a diverse range of technology. Apply modern principles, methodologies, tools, and systemic processed to support the launch of new business capabilities. Skills Considered a Plus: • Angular • Web Services • Jenkins • GIT • Java, J2EE and associated components (JSP, JMS) • C++ • Oracle/RDBMS/SQL
(JSP, JMS) • C++
But I admit php has come a very long way since php 4.
The only true answer to the OP's original question is
Like I said everyone's site is famous to them and the owner of the site.
Hey OP,
Not entirely sure what you consider a "famous" website, however, check out this website: https://stackshare.io/laravel
On there you can find who/company uses what, why they use it and what it stacks up to other frameworks/technology. I hope that helps you out!
@Vanish not sure about now, but FedEx used to use Drupal for their newsroom.
FedEx may be using Java now, but their shipping site was originally written in PHP by Visionary Systems. Not the API. The site itself.
notkutusu.com
@jlrdw I've told you a million times, don't exaggerate !
In Brazil, there are some nice projects going on using Laravel.
We have LeroyMerlin, a company that sells mainly supply for construction. As briefly explained in this video(unfortunately it is in Portuguese), they talk how they scaled up the "app" to support huge amounts of request. I consider it an example of 'big brand' site in our country.
Wow, kind of sad to see the responses to this... I work at Cisco, and we use Laravel on some of our projects. To say that PHP/Laravel is not good for enterprise level projects is partially false (mostly inaccurate).
From a DevOps perspective it can be a bit of a struggle to scale a Laravel/PHP application, but I can assure you that it is possible!
Maybe we should put together a guide to running Laravel/PHP applications at scale for enterprise?
Maybe we should put together a guide to running Laravel/PHP applications at scale for enterprise?
@ibourgeois I’d be keen to see that.
I'm sorry, why can't PHP run on big websites? Why can't PHP scale? Like concrete facts and information. "Language X is just better" is not a valid argument. Like I want some concrete arguments why PHP 7 cannot run enterprise, because I still haven't seen one in this entire thread.
Sure, PHP 4 and 5, well... sucked... But let's forget about history for now and focus on present. PHP 7 completely rocks. Sure it has it's quirks but no language is perfect. And it's not about the language. It's about the developer and system architecture. Use caching, proper code architecture, optimise your code, do load balancers (or whatever is done on the server, I'm stupid) and you're good to go.
Unless you have a properly built app running PHP 7 and Laravel 5.6 that doesn't handle a shit ton of requests/sec, I don't see the point of saying "PHP/Laravel cannot handle scaling". Also, I believe some parts of Facebook are still running on PHP?
The company I know of in Croatia has 100k registered users, a shit ton of database transactions per day, running a lot of external API and it works flawlessly on Laravel.
AAAAND finally... let's take a look at this dumpster fire that is Wordpress. It's code is probably the worst I have ever seen, and it still runs 30% of the web and does it well, some big players are using WP as their CMS of choice. If you get to the scale of Twitter or Facebook, you can hire yourself top devs that can scale your app with no hiccups. Until then, you don't have to worry.
I'm also confused by the scaling argument. Is it not an architecture subject matter? We run docker containers inside a kubernetes cluster and can scale up on demand. Several containers run well written PHP solutions.
@Web Confection United Rentals (https://unitedrentals.com Fortune 500 pre-covid) uses Laravel for one its many back-end APIs that support its Android app, iPhone app, and several web apps.
You won't find many (if any) major companies declaring they're "built" on Laravel because they aren't. But just because they aren't built on Laravel doesn't mean they don''t "utilize" Laravel.
At scale, you're going to see most companies implementing distributed systems and using something like a server-less distributed system that allows for several containerized services in the cloud.
One of those many services distributed across a large company's entire cloud infrastructure may be an API and that API may be implemented using Laravel.
In the case of United Rentals, one of - if not the - most important APIs is built using Laravel.
It's an extremely important service within the entire distributed systems architecture, but by NO means what so ever would I consider United Rentals "built with Laravel".
If anything, United Rentals is built on top of aws and the cloud - but even that's not entirely accurate as their are resources outside of the cloud infrastructure and the cloud acts as a middle man in a lot of cases between the clusters of databases and the 5 to 8 front end clients.
With that said, United Rentals uses Vue for its E-commerce front end, React for some sort of learning platform offered, Java for it's android app, Swift for its iphone, aws lambdas for handling serverless events coded in node/typescript/python, aws code pipeline, aws code deployment, aws codestar, aws codecommit etc... for continuous integration and continuous deployment.
United Rentals uses AWS SNS in which AWS Lambdas can subscribe to via their topics, and AWS SNS (Simple Notifications) are then able to be used to trigger lambda functions (aka server-less event handler) that handle every kind of event you can imagine. These events are queued up using AWS SQS and then I personally was responsible for getting them over to our sales force team.
Then you have to talk about the actual Virtual Private Cloud that internally wraps a subset of your system which is only accessible via the AWS API Gateway which requires AWS Route 52 to configure the DNS/nameservers/Hosting Zones and regions.
Then you've got to add in the storage. Optionally, you could go with AWS Dynamo DB if you choose the NoSQL route as well as add in the AWS service for a relational database to use it instead or even use both databases at the same time - which often cases is the right decision in large scale applications. What if you want to store files/documents? AWS S3 is a solid choice - then you have a lot of data in large scale applications so you're possibly going to need to create an incredibly cheap way to store data that is outdated but still needs to be kept. Needing cheap instead of efficient, you may choose to use AWS Glacier.
You also have to take into account access, who is able to access these AWS services - what about the access allowed for dev API keys and secrets when they programmatically use AWS? IAM roles allow you to create roles that have permissions, these roles can be assigned and allow for resource policies to control access.
Then you have to talk about keeping all of this infrastructure supportable over time, if you had multiple teams working in the same codebase without version control the app would break extremely often. Same goes for cloud infrastructure within distributed systems, so the idea of "Infrastructure as Code" comes into play. You create your infrastructure using Definition files and version control it like you would any other codebase. These definition files define what your cloud infrastructure amounts to and ultimately supplies a way to maintain it in a way that doesn't break constantly.
Okay, so what else? Well, how's the whole computation thing work in the cloud? Example? Laravel can use vagrant as a virtual machine via Homestead...but how's that work when there are 100 services and only one of them is Laravel? Do you boot up 100 Vagrant Virtual Machines like homestead and manage/configure them while keeping them up to date?
Hell to the f no you don't, you'd probably go broke using virtual machines and it'd be a huge headache - instead you use containers like docker.
Docker containers allow you to separate the services infrastructure dependencies from the code itself. Ex: a single server doesn't, nor should it, depend on any other services runtime.
You can use Node in one service via a container that pulls and runs Node, Python in the next via a container that pulls and runs Python, and PHP in another one because that's what it needs to run some good ol' Laravel.
The MySql/NoSQL database would also be its own service and thus would use their own containers to support their own runtimes respectively.
There's also the AWS SAM framework for devs to easily invoke and deploy server-less infrastructure code locally and directly deploy it to the cloud.
Now with a part of the distributed system explained, I'm going to end with a final portion of that distributed system that matters more than most.
The ability to duplicate/replicate a given service to allow for horizontal scaling needs to be set up.
How's this work?
Well that Laravel app being its own service with its own docker container isn't the only thing that a service in the cloud is.
A service with a Laravel app and associated docker container in the cloud should be duplicated multiple times over. The cloud allows us to create, for example, 6 instances of the same service.
In this 6 instance example, this means we have 6 Laravel Apps each with its own docker container. This allows us to put a load balancer at the entry point so that when the IP address to use the Laravel service is hit, the load balancer will actually distribute the traffic to any one of the many instances of our Laravel App.
We're able to configure the replication of instances for any service to automatically scale and descale based on traffic demands so that we are optimally using computational resources while also being able to scale without losing any of the speed that we had when the traffic was extremely low.
One user or one hundred million users, by using the cloud we're able to add multiple services into a complex distributed system while maintaining the speed of an application via horizontal scaling and improve site reliability by having multiple instances that allow traffic to hit another instance of the same service if a specific one out of the many fails.
Now, knowing what you know after reading this post, would you call United Rentals a "Laravel Application"? Laravel is a single, very important service - but to call it a Laravel application would be an incredible understatement.
This doesn't mean Laravel isn't used at scale, simply means scale requires an entirely different way of building applications that goes beyond any single framework - including Laravel.
Also, not huge yet - but https://cleancode.studio was approved for a $5k AWS grant and will be using Laravel for one of its backend API s as well (totally a zero shame self-promotion, but hey - convince me this isn't more of a blog than a comment and blogs are backlink worthy - aka self-plug justified :D )
Please or to participate in this conversation.