I forgot which is the first version of ABP that replace Ocelot to Yarp, do you know about it?
4 Answer(s)
-
0
ABP switched the Microservice Startup Template API Gateway from Ocelot to YARP starting with ABP v8.0 (i.e., YARP is available with ABP v8.0+).
- So, the first ABP version that replaced Ocelot with YARP is: v8.0.
You can see it explicitly stated in the migration guide: “Since YARP is available with ABP v8.0+, you will need to update…”
Sources:
- https://abp.io/docs/latest/release-info/migration-guides/pro/migrating-to-yarp
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
-
0
We have a project currently is ABP 8.1.3 which still uses Ocelot, we are going to upgrade it to ABP 10.1.0, do we have to upgrade to Yarp? Recommendation?
-
0
- You don’t have to upgrade to YARP just because you’re upgrading ABP to 10.1.0. ABP’s own migration guide says that when ABP switched the microservice template gateway from Ocelot to YARP, existing solutions don’t need to make any changes, but ABP recommends YARP because Ocelot is not actively maintained.
- Recommendation: If your API Gateway is still on Ocelot in ABP 8.1.3 and you’re already doing a major upgrade to 10.1.0, it’s a good time to plan migrating to YARP (to align with ABP’s newer microservice template and avoid depending on an unmaintained gateway). That said, if you need the lowest-risk upgrade path, you can upgrade ABP first and keep Ocelot, then migrate the gateway in a separate, controlled change.
Practical approach (recommended sequence)
- Upgrade solution/packages from 8.1.3 → 10.1.0 and keep the gateway as-is (Ocelot) to reduce variables.
- After everything is stable, migrate Ocelot → YARP using ABP’s “Migrating to YARP” doc and test routing/auth flows thoroughly (especially if you have custom claims/headers, rate limiting, WebSockets, or advanced routing rules).
Links (verified):
- https://abp.io/docs/latest/release-info/migration-guides/abp-8-0
- https://abp.io/docs/latest/release-info/migration-guides/pro/migrating-to-yarp
- https://abp.io/docs/latest/release-info/migration-guides/abp-10-0
- https://abp.io/docs/latest/release-info/migration-guides/abp-10-1
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
-
0
hi
Switch Ocelot to YARP for the API Gateway Until this version, ABP Commercial was using the Ocelot for the API Gateway, in the Microservice Startup Template. Since the Ocelot library is not actively maintained, we have searched for an alternative and decided to switch from Ocelot to YARP for the API Gateway. YARP is maintained by Microsoft and is actively being developed and seems a better alternative than Ocelot and provides the same feature stack and even more.
You can read the Migrating to YARP documentation for migrating your existing microservice application's API Gateway from Ocelot to YARP.
We have made the all related changes in the Microservice Startup Template, and also updated the documentation, which you can read here. https://abp.io/docs/commercial/8.0/startup-templates/microservice/gateways
https://abp.io/community/articles/abp.io-platform-8.0-rc-has-been-published-3d8z8i16#switch-ocelot-to-yarp-for-the-api-gateway&gsc.tab=0
Is your project a microservice?
Thanks.
