With platforms, you really need to figure out what all the platforms are capable of. They cannot do, for example, in the manufacturing space, machine data. They can show the machine data, however, they cannot store it.

In general, they have capabilities where they limit themselves, intentionally. 

We have internal and external users. On the manufacturing side, Manufacturing companies usually have use cases that will have more internal users versus external, which means they are dealing with factory workers. Per factory, in that case, you may have 50 to 100 people. We've built apps for an average of 100 to 200 users per factory.

We are going full-scale on Mendix right now. The way I've seen the other products, anywhere where we have manufacturing and SAP side of the product coming in, we are proposing Mendix. We are pushing Mendix 100%.

Mendix is a scalable platform. You can scale it up anytime. The platform provides you with much flexibility, and my rating for it in terms of scalability is nine out of ten.

I would keep it a medium on scalability. With small numbers of users, it is very nimble and operates fast, but when you get a whole lot of users in there, transaction speed goes down.

The number of users is relatively low. It is probably in the ballpark of under a hundred. It is currently for small cases for us. It is for small SharePoint replacements and small dashboards, but there are a lot of viewers of what's happening live with the system, whether things are up or down, and what they are doing for health monitoring of equipment, etc. We probably will increase its usage.

Mendix is easy to scale for typical business applications. It's horizontally and vertically scalable.

It used to be mainly for medium and large companies, but the new pricing makes it much more accessible. Now, it's suitable for the whole spectrum, from small to large.

The free version has some restricted functions. It doesn't give you access to the full solution. 

It's a scalable product.

I didn't really build something big by myself on it. I've seen with some applications if you respect good practices, if you don't overwhelm, if you put 100 entities in a module or something, and if you separate things properly, you can scale.

We have a new platform, which we put into production about half a year ago, and we had an initial 10 sort-of automated processes on top of it at the moment. It's going to grow, obviously. That's the idea.

So far, we are happy with the potential it has for scaling, although in practice we have not yet tried.

The tool is scalable. We had a single application in development, and there were two developers with 15 end users.

Looking at the architecture, scalability is going to be a challenge. I was part of the program, which I could not finish as I left the company. Yeah. Scalability-wise, I do see the technical approach that platform offers. Scalability will always be a question mark for me. I don't have data to prove whether it is not scalable. However, I am aware that it will be a challenge to scale. 

There are two types of scalability we're talking about. One is putting more and more and more and more processes on top of Mendix. That should not be a challenge. However, taking one process, taking one application, and scaling it to multiple countries, is where I see this platform struggling. However, with the cloud version, scaling may be simpler. 

The product can scale and expand if you need it to.

We're planning to use it for 100 people.

The scalability potential is very good. If you want to expand it, you can. 

It's only scalable vertically until you get to an enterprise license. Then, you have horizontal and vertical scalability. I'd recommend in general that people get an enterprise license.

We use it internally for maybe 400 of our employees, however, depending on what its use case is, it could be everybody. My largest one has 4,000 people they supply using it.

The scalability of Mendix is good. However, whenever we deploy the application, it's heavily weighted on the server. It is not a light solution.

We have approximately 100 people using this solution in my organization.

It is quite scalable. I'd rate the ability to expand eight out of ten. The connectors can enter various products in Microsoft, especially here in the Gulf.

We use Kubernetes environment and the scalability of Mendix depends on this environment. 

This product is scalable and it's relatively easy to scale. Because of its architecture, it can't scale like microservices that are designed for scaling across the globe, but Mendix has some horizontal and vertical scaling built in. It's not on the same level that you would get with a native cloud first node app. It's a little bit more limited, but there are still scaling options. 

The Dubai Municipality makes use of Mendix, as well as five out of 40 ministries. They have transferred their core applications to Mendix in their entirety. The remainder are in a transitional phase and this should be completed throughout the entire government of Jordan within five to six years. 

The solution can scale.

Of course, you need to do things for that yourself. It's not that Mendix has it in its platform. It gives you options to help you with your scalability. However, you need to do quite a lot for yourself as well.

I'm working for a test company and we work with quite a few clients. We have seven clients that use Mendix.

Mendix is slightly less scalable than I'd like.

We have 30 internal users. The issue for us is, from a low-code interface perspective, how do we deal with external users?

We are able to run very high performance applications on very small Mendix app containers. That is because we design our solutions to be high performance from a design point of view. We have not used the Mendix horizontal and vertical scaling options that they provide. Therefore, I am not an experienced user with scalability, but I do know that we can make already quite high performance applications with a single app containers and they can be scaled vertically and horizontally. 

Mendix is quite powerful. There are some limitations in Mendix. On the database level, there are still some layers between Mendix and the database. This means that some actions are not efficient, which might seem to be, and they have designed now a stateless architecture which also put some limitations of speed if you use a single instance. However, the stateless architecture allows you to spread horizontally your load. So, it has benefits and drawbacks. In general, it is good enough for what Mendix is supposed to be used for. There have not been any projects where we could not do them because of performance reasons.

It is a scalable solution.

In the past, I encountered scalability issues that caused stability issues. Mendix can scale to multiple application servers but at the time it could not scale to more database servers, the only solution was, to add more resources to the single available database server.

I do believe that Mendix is trying to solve this with HP Helion and Cloud Foundry solutions which are horizontal and vertical scalable. I however haven't had any experience with these platforms in combination with Mendix yet.

There have been no issues scaling it for our customer.

I have had no issues scaling it for my needs.

Yes, the Mendix Cloud out-of-the-box does not support autoscaling.

Scalability requires a bit more expertise but is not insurmountable, at least not for any of the products we have developed, which includes Big Data climate sensor systems, GIS, Risk Decisioning, Lead/Queue Management, Loan Origination/Loan Applications both online- and agent-based channels like phone/email/web/mobile etc.

Generally there have been no issues scaling. Keep in mind that Mendix runs on a RDBMS as its main persistent store and as such will scale with the data base. We find that the Mendix App server is only the bottle neck on tight loops over LOTS of data and when using dynamically calculated values. However, this is not typical use cases for Mendix and can be avoided by using microservices that do tight loop/ETL, simulation etc. work loads and leave complex business processes to Mendix.

No.

We've had no issues scaling it for our needs.

I think that right now, the scale-out is quite ok. It is scalable.

We have more than twenty users including developers, system handlers, business analysts, testers, and DevOps. The DevOps team is really what really takes it ahead.

In terms of usage, there is a lot of interest in low-code and no-code tools. There are even other tools like OutSystems and others. There are also automation tools, such as RPA (Robotic Process Automation) tools. It is still an evolving market.

There have been scalability issues. Think about scalability early on, so you don't have to refactor your design when you are already in production.

We have had no issues scaling it to our needs. You can either scale by using multi tenancy or as we did use the same model for multple customers.

We have had no issues scaling it to our needs.

We had no issues scaling for the needs of our customers.

There were memory leaks after a week of it being live. We need to clear the memory once a week.

We haven't had any issues with scalability.

It is very good.

When using custom build widget, Javascript and Java Action, stability depends more on using the correct versions of SDK's, libraries etc.

With v3.2.1 we had some scalability issues which we resolved by upgrading to a later. This upgrade made our application a lot more scalable.

No