useful for all scenes, i just write edge as a example, because edge has the
most serious problem with jvm meta overflow
edge and normal microservice share the same mechanism
compatible problem include:
- some customer's handler and filter customization maybe need some
change, because:
What's the difference between the strong type and weak type?
>From the mail I can tell the weak type is useful in the edge service,
can we just us it in the edge service?
BTW, We need to be care if there is a API break change, heading to
version 2.0.0 is a good way, is there any other big change
currently, core mechanism is strong type
that caused to generate class dynamically in many special classloader, it's
dangerous:
- need to generate almost all business classes in edge, maybe cause jvm
meta overflow
- unable to support advanced features of swagger, such as allOf
-
