Michael Mota

Automations are what makes a CRM powerful. With Celery and RabbitMQ we've been able to make powerful automations that truly works for our clients. Such as for example, automatic daily reports, reminders for their activities, important notifications regarding their client activities and actions on the website and more.

We use Celery basically for everything that needs to be scheduled for the future, and using RabbitMQ as our Queue-broker is amazing since it fully integrates with Django and Celery storing on our database results of the tasks done so we can see if anything fails immediately.

I've been using Django for quite a long time and in my opinion I would never switch from it. My company is currently using Django with REST framework and a part in GraphQL using Graphene. On the frontend we use Next.js and so far everything has been running quite good. I've found limitations but manage to solve it.

As someone mentioned before, if you are comfortable with Django, don't switch. There's no need since with django you can basically achieve anything. Of course this will depend on the project you want to build, but the scalability and flexibility django can offer it's just out of this world. (Don't want to sound like a fan boy haha but it really is).

I honestly don't know if this could help but, I'll speak from my similar experience with Django. I had to do for a client a dynamic map in real time so that users can select their seats for a specific event. In the first MVP tickets sold in less then 10 minutes, over 400 users at the same time online trying to buy the seats. (I mention this to get in the context of why I used it).

We achieved this with Django, Socket.IO, PostgreSQL and for the frontend React. With the power of Socket IO we manage to achieve a real time connection with the database with a reaaally low response time.

The drawbacks of Django are that everyone knows that Django is not really good for real-time activities but in combination with Socket.IO this can be achieve really good.

I hope that in some way I helped. 👍🏼

We use InVision because in AlterEstate, companies can request us a specific design for their website instead of one of our pre-made themes (for more customization purposes).

So with InVision our design team can have meetings with our clients online sketching and deciding important matters about their websites. All this in a real time board that really makes the experience with our customer more unique, new (at least in our country) and more connected.

We are growing daily, and as we grow we find more things to keep track of. With Slack we've manage to create a simple integration to notify us on important matters of our software, for example, when a new user is created on any of our clients (automated billing process with Stripe).

When any of our servers are increasing the memory/cpu usage, also daily reports of all of our clients activities related to their website (Visits received, new leads generated, deals won/lost etc...)

We recently implemented GraphQL because we needed to build dynamic reports based on the user preference and configuration, this was extremely complicated with our actual RESTful API, the code started to get harder to maintain but switching to GraphQL helped us to to build beautiful reports for our clients that truly help them make data-driven decisions.

Our goal is to implemented GraphQL in the whole platform eventually, we are using Graphene , a python library for Django .

We use notion.so because it's beautiful, fast, easy, friendly and portable. We use for our clients, for our team, for my personal life, basically for everything.

The fact that you can create a Kanban in matter of seconds but also turn it in a table if you want it and at the same time share it in seconds with your client/team it's priceless, real-time editing also makes it beautiful for brainstorm meetings so everyone involved in it it's synced with whats being discussed.

Having a single Next.js that handles several websites at the same time, with a lot of custom-unique components can be a pain in the a**, with TypeScript our team can see what props are needed and what kind of data needs to be passed to it in order to work correctly.

We use AWS Lambda mainly in combination with Amazon S3 to resize the images that our clients upload in our platform. Working with real estate agents means lots and lots of photos that need to be resized when they are on a website so that the visitors of our clients can navigate on a website that it's fast and beautiful at the same time.

We use Amazon S3 because it's the best way to store the users static content such as images and videos, and with the help of some Lambda functions we are able to make image-resize on the fly without having to put our servers to work on that task.