1.Cache does not support redis custom TTL, the official has not yet resolved.
Workaround: Solved by implementing rediswriter yourself.
2.Cache does not support Redis' cache statistics.
Solution: no solution, ignore it.
3. JPA does not support dynamic generation of data source related beans.
Solution: no solution, ignore it.
4. JPA and hibernate do not have webflux support, nor will they be available in the long run.
Solution: no solution, ignore it.
5. Druid does not support webflux's console page. Issue has been submitted.
Solution: Close the druid web console page.
6. Druid SQL firewall does not support sybase, specifically, it does not recognize two points of sybase, such as CIS..contacts cannot be recognized.
Solution: Turn off the SQL firewall.
7. Druid's SQL log does not support sybase.
Solution: Customize druid datasource logFilter solution.
8. Druid does not support database statistics of spring boot2.0.
Solution: Customize DataSourcePoolMetadataProvider.
9. ObjectMapper deserialization loses nested types, nested types are always deserialized as LinkedHashMap.
Solution: The solution was originally very simple, but considering to be compatible with existing applications, so...no solution. It can only be solved case by case.
10.Swagger does not support webflux.
Solution: Compile the swagger official master branch code by yourself. Although it is unstable, it can be started. Wait for the stable version to be released.
11. Swagger web flux does not support context path.
Solution: No solution yet, an issue has been submitted to the swagger author. Recompile the swagger master branch code after the issue is closed.
12. Webflux call chain tracking problem, no out-of-box solution is available.
Solution: Learn from the solution of spring-cloud-sleuth.
13. Some existing backend pages cannot be upgraded to thymeleaf 3.0.
Solution: no solution, ignore it.
14. Spring cloud does not support spring boot2.0.
Solution: Use the milestone version and wait for the release to be released.