Refit
dapr
Refit | dapr | |
---|---|---|
33 | 79 | |
8,108 | 23,313 | |
1.4% | 0.6% | |
8.2 | 9.7 | |
4 days ago | 1 day ago | |
C# | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Refit
-
Exception Handling in C# Methods returning object
A lot of people have given you good replies, but have you looked at Refit?
-
Http calls on mobile, what is the preferred way / best practice
Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?
-
Refactor your dotNET HTTP Clients to Typed HTTP Clients
Define a Refit client interface with the following for each API endpoint, e.g. GET /foo:
-
HttpClient best approach
Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.
-
What your hidden nuget gems ?
Refit - simple, typed REST clients: https://github.com/reactiveui/refit
-
how to structure code for rest api calls
I'd advise using this https://github.com/reactiveui/refit tool for HTTP requests. It saves a lot of time for serialization, deserialization and exception handling.
-
Roadmap for transition from Java
Use Refit, and let manage the live of HttpClient. Also, Refit will give you a strongly typed client around an API. All you have to write is the interface. Ain't that neat ? If you can't, use the HttpClientFactory to create the HttpClient instance: https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests
-
ASP.NET Core - how to properly make a GET request?
Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.
-
Integration tests without API dependencies with ASP.NET Core and WireMock.Net
The controller is simple and use the Refit library to abstract the PokéAPI call and then, returns the data.
-
I love refit
To be fair, Refit is pretty great.
dapr
-
Join the Diagrid Catalyst AWS Hackathon!
Diagrid Catalyst is a Developer API platform providing a brand-new approach to distributed application development. Using the Catalyst APIs, powered by the Dapr open source project, developers can overcome the complexity of rewriting common software patterns and achieve higher productivity by offloading infrastructure concerns from their code to Catalyst.
- Dapr: Microservices API
-
Interesting projects using WebAssembly
The following two examples are open-source projects maintained by Fermyon with contributions from companies like Microsoft and SUSE. The first is Spin, which allows us to use WebAssembly to create Serverless applications. The second, SpinKube, combines some of the topics I'm most excited about these days: WebAssembly and Kubernetes Operators :) The official website says, "By running applications in the Wasm abstraction layer, SpinKube offers developers a more powerful, efficient, and scalable way to optimize application delivery on Kubernetes." By the way, this post shows how to integrate SpinKube with Dapr, another technology I'm very interested in, and I should write some posts soon.
-
The Ambassador Pattern
Speaking of this has anyone had much experience with Dapr (https://dapr.io/) before?
I always thought this was a particularly interesting approach from Microsoft where they use this pattern to essentially take the complexity of micro services and instead try and keep it as simple as a normal .NET application but (and I think this is the clever part) in both a vendor and language neutral way.
But all of a sudden it means you can start removing all kinds of cruft and random SDKs from your codebase and push almost all of your interactions with the outside world into something like this .
-
Comparing Azure Functions vs Dapr on Azure Container Apps
Azure Container Apps hosting of Azure Functions is a way to host Azure Functions directly in Container Apps - additionally to App Service with and without containers. This offering also adds some Container Apps built-in capabilities like the Dapr microservices framework which would allow for mixing microservices workloads on the same environment with Functions.
-
Episode 150: myNewsWrap – SAP and Microsoft
Having containers is nice but everything (well ... nearly everything 😉) gets better with Dapr as an outstanding tool for app development in the container-based area. Here we go what might be worth a look:
-
Using DARP in production?
Anyone using or planing to use darp Distributed application platform runtime as a microservices platform? https://dapr.io/
-
Ensuring Seamless Operations: Troubleshooting and Resolving Dapr Certificate Expiry
A CNCF project, the Distributed Application Runtime (Dapr) provides APIs that simplify microservice connectivity. Whether your communication pattern is service to service invocation or pub/sub messaging, Dapr helps you write resilient and secured microservices. Essentially, it provides a new way to build microservices by using the reusable blocks implemented as sidecars.
-
Understanding the Dapr workflow engine and workflow patterns in .NET (1hr webinar)
Dapr is a runtime that implements common patterns such as pub/sub, state storage, etc. It runs as a sidecar to your app. Your app then interfaces with it using an sdk or http calls to use said patterns instead of implementing those patterns directly yourself. Seems pretty cool to me, but you can find out more at https://dapr.io/.
-
Is Dapr actually used by anyone?
- Over 21k stars on GitHub, see the core repo and devstats.
What are some alternatives?
RestSharp - Simple REST and HTTP API Client for .NET
MassTransit - Distributed Application Framework for .NET
Flurl.Http - Fluent URL builder and testable HTTP client for .NET
camel-k - Apache Camel K is a lightweight integration platform, born on Kubernetes, with serverless superpowers
RestEase - Easy-to-use typesafe REST API client library for .NET Standard 1.1 and .NET Framework 4.5 and higher, which is simple and customisable. Inspired by Refit
tye - Tye is a tool that makes developing, testing, and deploying microservices and distributed applications easier. Project Tye includes a local orchestrator to make developing microservices easier and the ability to deploy microservices to Kubernetes with minimal configuration.
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
Simple.OData.Client
Nomad - Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.
Ocelot - .NET API Gateway
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET