Can large SAAS applications be created in Phoenix?

connected-cjohnston

I am in the process of learning Elixir and Phoenix, and so far, all the example apps that I see use LiveView and are small, dynamic single page applications that are all some variation on chat apps. As such, I have a few questions:

Are regular phoenix controllers still usable or have they been basically deprecated with LiveView being the way forward?
With LiveView, is it possible to create large scale SAAP style web applications with Phoenix or are small, dynamic apps with one or two controllers the sweet spot for phoenix?
Assuming one can still use regular controllers, are there any good resources out there for how to build multi-controller web apps with phoenix 1.7? Unfortunately, all the guides that I have found so far use LiveView and mostly skip over how to work with regular controllers.

5 comments

/phoenix

2 2145 5

2023-05-24 15:30:56 UTC

Showing Posts 1 to 5

Show Best Posts
Show All (oldest first)
Show All (newest first)

sodapopcan

Hello and welcome!

The Official Phoenix Guides is really the best resource. Elixir’s documentation is pretty fantastic and, if you’re not used to that coming from other ecosystems, I would always look there first. Controllers are absolutely still usable and will not be deprecated (websockets can’t set session data so they are at least necessary for that kind of thing). The Contexts section goes in depth about building an end-to-end feature and it uses controllers.

As for building a large SAAP app I can’t speak from experience there. Phoenix should be quite capable of building very large applications, though coming from me that is merely speculative based on others’ reports of their experience

Here is a somewhat verbose description of hexdocs I gave to someone else who asked a similar question recently (because I didn’t notice these things right away, ha).

Post #1

kokolegorille

Yes it is still usable. There should be a page_controller created by default in any new Phoenix 1.7 project..

But now, previous templates, views and controllers are colocated in a controllers folder.

When You create API, You only have only controllers, no Liveview

Post #2

neilberkman

As for building a large SAAP app I can’t speak from experience there. Phoenix should be quite capable of building very large applications, though coming from me that is merely speculative based on others’ reports of their experience

I’m currently leading the development of a SaaS product, a CRM for commercial real estate brokers, using LiveView. The application is live, serving real customers, and I couldn’t be happier with the choice. The UI includes Kanban boards, multi-step forms and other fairly involved components.

I’d suggesting watching this conference talk: https://www.youtube.com/watch?v=XzAupUHiryg While it’s not a SaaS product, cars.com is a large-scale, very high traffic ecommerce site. The talk describes some issues they had when they cut over, but this is to be expected when completely rewriting an existing high-traffic application.

Post #3

connected-cjohnston

Thank you for the link to the Contexts section of the docs. It looks like what i am looking for. I had not yet visited that page in my exploration.

Post #4

matthieuchabert

Hi Chris!

You can definitely mix Liveview and controllers depending on your needs. Controllers are the only option if you serve an SPA for example.

About large scale Phoenix applications, at my company, we have a big monolith (~2000 Elixir files) that serves 4 web applications on different domains. We couldn’t be happier with our choice to build that with Elixir and Phoenix.

We started to use controllers a few years ago and slowly migrated them to Liveview. Honestly we don’t see the need for controllers anymore because we got used to working with Liveview

Post #5

— All posts loaded —