Spring Boot could improve its integration with the major cloud providers. Connectivity with cloud solutions isn't easy compared to other frameworks like Django and Python.

I need to connect to GCP, so I would like to have one simple dependency that I can include to immediately connect to GCP, so I don't need to go through all the configuration steps. 

The current state of Spring Boot's cloud layer requires further development, especially for collecting Java functions for cloud platforms like GCP Cloudground. Having to write every single API request in a single class can be a cumbersome and time-consuming task that is not ideal for Java developers. Additionally, having all API calls in one class and making it the main class presents problems with package visibility. Therefore, there is much room for improvement in the Spring Cloud area.

It would be beneficial to have a cloud experience solution that includes a JPA repository in Spring Boot's cloud layer. This would eliminate the need to switch back to template JDMV and provide a more streamlined approach to developing applications. Additionally, improvements in the security layer are necessary, such as implementing SSL, which is of utmost importance.

We have specific algorithms for our Load Balancer or API gateway. So those things, if they could make it more precise, that would be beneficial. Sometimes when we are under pressure or any new person who looks into that stuff, we'll get confused or scared because of some difficulties in understanding Which algorithm needs to be used to implement a Load Balancer. When when we Yeah. Because when we say circuit breaker, we need to use it, and then the user gets a blank circuit breaker. This means we are saying the circuit breaker needs to be moved, and then that circuit breaker needs to be elaborated more. What type of algorithm should I do, and what exactly do I need to get done so that this circuit breaker can help me to resolve my issue? Because, you know, because if you go for the circuit breaker, it will ask to open the new tab, you know, since it will check. If the service is not responding, it will wait and go for another connection. So in similar words, if they can explain it a bit more, that will be helpful. Everyone could do their own Google stuff, and they will get it, but they need help understanding how this could help them to resolve the issue. It will be good if Spring Boot provides information about real-time use cases.

They should integrate the solution with more AI and machine learning platforms. In addition, its integration with Kubernetes needs improvement. Also, they should add documentation specifying project-wise integrations. Along with this, they should include more configurations and streamline the implementation process.

Spring Boot is a bounded framework. The services we develop are purely synchronous services, so there's a blocking and waiting state. This is a big problem in microservices. To avoid this problem, we have to make the service a reactive session. It has to be reactive to a particular load, particular condition, or based on the number of requests hitting the particular service. All these factors make the service a reactor. There's another module in which Spring Boot provides spring reflex.

This module enables the reactiveness of the service, meaning that it eliminates the blocking and waiting state. For example, if you're sending a get operation or a post operation, there won't be any waiting for it to actually hit that particular network to get the data from another service. It continuously flows the request, and there is a zero waiting pack. Vert.x is another good framework where there are similar features or similar benefits with having a reactive session.

Spring Boot is a license resource, so it's a framework where we can customize our solution or a particular requirement to build a good solution using Spring Boot. But it's an opinionated framework, meaning that it's completely bounded. You have only one direction to find a solution, whereas Vert.x is an unopinionated framework.

Unopinionated is a kind of a toolkit where you can have more optimization and a more flexible solution, which is suitable to your requirements. In Spring Boot, the opportunities are limited. With Vert.x and other programming tools, we have multiple options to explore the solution in a different way and achieve a nonfunctional requirement of thousands transactions in a second. Spring Boot might not support this kind of non-functional requirement. Vert.X is a very good solution to solve critical NFRs for a particular application.

Building a new product in Spring Boot can take a long time since the solution uses reflection. This is one area the solution could be improved. 

The solution needs more applicable control for large-scale application development. It is a time-consuming process to convert a framework to an application. Also, it requires integration with other platforms, making it even more complicated. We cannot use it directly in existing projects utilizing the framework. These particular areas need improvement.

This is a really good solution for me and I can't think of anything that can be improved.

In terms of the Spring Boot application, the application's startup time needs to be improved. We'd like to see more speed and better performance. 

We'd like them to develop more supporting testing. We'd like to see it be more flexible.

It would be ideal if they continued to prioritize security.

They should ensure that auto-configuration related to Spring MVC will be added into any new features.

This solution could be improved if there were more libraries available. We would also like more mobile platform functionality using low levels of code. 

They should include tutorial videos for understanding new technologies.

Perhaps an even lighter-weight, leaner version could be made available, to compete with alternative solutions, such as NodeJS.

It would also be extremely helpful if hand-holding templates were provided, to quickly guide new developers through the entire end-to-end process of developing a solution with Spring Boot. These aids could be in question or checkbox answer format, which would then trigger the appropriate guides. The guides should be geared to developer tasks. For example, after the neophyte Spring Boot developer answers some questions, the guide might say, "OK, then, you will want to put your MongoDB queries in the MongoDB Repository that you have created. You can use this @Query format..."

Spring Boot's cost could be cheaper.

The product uses up a lot of memory, which is an issue. We don't need such complicated frameworks. I don't use Java anymore. 

The performance could be better.

I'm not sure if there are any features that need to be added. 

We'd like to have fewer updates. 

If you want to create large microservices applications, you need to connect several applications and services to each other. It is very complicated, and Spring Boot does not have an integrated solution for it.

It would be good to have documentation on Spring Reactive to better understand it.

Spring Boot can improve the dependency tree that we use for libraries. It would be helpful if it was less complex.

Spring Boot is okay right now, but my team is looking for some integration where you can make a call to the JMS messaging service and other types of third-party integrations. If the integration with Spring Boot is improved, that would make the tool better.

What I'd like to see in the next release of Spring Boot is its integration or tie-up with messaging servers and third-party EFPs, as that would make it very good and more competitive versus other new solutions in the market.

Nothing really comes to mind in terms of areas of improvement. It works well. There's nothing that stands out that I would look to be improved with that software.

The tool's documentation could be improved, especially by tying it back to frequently asked questions and issues users have. A feedback loop in which the documentation targets the most commonly asked user questions would make using the solution easier. Essentially, I want a more user-centered approach to documentation rather than a purely technical focus.

The UI could be better, though, like many users, we don't use Spring Boot's UI functionality; we use an Angular front-end, and Spring is a backend layer. There are alternatives to using the solution's UI.

The solution has some vulnerabilities and fails our security audits, forcing us to keep fixing the solution.

Spring Boot is based on convention over configuration. Therefore, sometimes it seems that everything happens magically. It's difficult to explain to junior developers what it does under the hood.

There are no missing features at this time.

The cloud packaging is not very straightforward, I would say. For example, integrating with Azure or a microservice architecture or cloud-based architecture is ard. If they could improve and provide a whole package at once would be great.

This solution could be improved if it offered greater integration and was more compatible with other solutions. For this reason, we have moved to Microsoft. 

With the boom of AI and machine learning, there is a need for a lot simpler integrations with them. The solution should have basic data models. There were regression and classification models before introducing data models back, and I feel we need some plugins to help to make it possible. In general, I want to see some integration in Spring Boot with artificial intelligence products.

The database connectivity could be better in terms of dealing with multi-tenant systems. If that could be simplified, that would be better. Currently, we have to use a customer's implementation. 

I'm not missing any features. 

Spring Boot could improve the interface, error handling, and integration performance.

The solution could improve its flexibility.

I'm not one who is really obsessed with Spring Boot. It's a tool. But at the same time, I would rather use other things like a BPMN engine to do the work because Spring Boot is lacking visibility in terms of how that business process or business rule would look within your application. Because everything has been embedded within the code itself, it disables the visibility and the ability to maintain or even support a specific functionality in a user-friendly manner, where a developer can come up and just adjust that part of that process.

I'd rather go for a BPMN tool or engine that will reduce development time, rather than spending the whole time writing a tiny function for linking activities or tasks together.
I would rather use a BPMN engine just to focus on the business link and, at the same time, to have that type of visibility and agility, not to mention, of course, the consistency between consumer processes and the business ability.

I think that security is a delicate issue in this product. It's not as easy as in other technologies so unless you already have something configured it can't be done with a junior developer. You need some experience to do that properly and to understand how Spring security works.

In addition, as many developers say, sometimes you can see too much magic without really understanding what's happening under the hood. This is the main benefit of Spring Boot, but also a disadvantage in the event that the convention doesn't work and needs to be customized. 

An additional feature they could consider would be the ability to reload properties without having to restart the application. It's one of the things I miss most. There is a solution that requires cloud tools, but there's no way to do it with a simple configuration.

This is not a tool for beginners. You need to know and understand it well.

It needs to be simplified, more user-friendly.

Spring Boot is only for lightweight components. You cannot have large applications on it.

If the binary size is large then you have to ensure that the services that are designed are very lightweight.  For example, if there are ten components, you have to divide them into ten and not into one. There needs to be a logical separation.

I would like to see the size of the code improved and the framework. We don't always realize how much we are loading into the microservice. There should be some limitations in place to indicate whether the code size should not exceed a certain amount and should not compile itself.

I feel like communication has to be increased. For example, communicating between different services from the third party layers or with the legacy applications. But, it's getting mature right now, but there are some communication patterns that are getting with Spring Boot.

The cross framework compatibility has some shortcomings. With JUnit Test Runner and Spring Boot, it's really tedious to make them both work to write the test cases.

We'd like to see them get better at securing apps. 

For example, when you want to do authentication, it would be ideal if there was a way to do two-step verification. 

We don't really need any new features.

When we change versions, we run into issues. 

The product could be improved by supporting and integrating Hadoop. A year ago Spring Boot announced that they were removing Hadoop support from the product but many software companies work with Hadoop and Cassandra, and I really think that Spring Boot should renew the Hadoop connection. 

I would like to see more integration in this solution.

The configuration moving down from a command key is difficult. If you are doing configurations and adding items, it can become a little challenging.

The security could be simplified.