Bitrise Reviews

gRPC Reviews

Bitrise mentions (11)

• iOS CI/CD Evolution: From Bitrise to GitHub Actions Migration Study

  Some time ago we had a client that asked us to migrate his whole mobile CI/CD flow from Bitrise to GitHub actions. The project was a React Native, iOS-targeted application. - Source: dev.to / 10 months ago

• Best CI/CD tools for React Native

  In this article, we briefly discussed some popular CI/CD platforms for React Native and why they are crucial in the programming world. We also included some honorable mentions, Jenkins CI and Bitrise, in our comparison table. It is important to remember that every project is different, and therefore it is important to evaluate each tool’s advantages and disadvantages. - Source: dev.to / 10 months ago

• Jobber's React Native migration - Success!

  Unified both iOS and Android building to bitrise for our mobile build pipeline. Much better than the older Buddy Build system which was purchased by Apple, put into hibernation, and then shut down by Apple. - Source: dev.to / 12 months ago

• Continuous Integration and Deployment: A Developer's Best Friends

  Bitrise: Bitrise is a CI/CD platform specifically designed for mobile app development. It offers a range of pre-configured workflows and integrations with popular development tools, making it an excellent choice for junior developers working on mobile projects. - Source: dev.to / about 1 year ago

• Beware of Xcode 14.3

  You can (temporarily) work around the issue by using an external build service, like bitrise.io, or EAS. That way, you can use newer xcode to build a development or production version of your app. Source: about 1 year ago

gRPC mentions (89)

• Best Practices for Building Microservices with NestJS

  Choose a consistent communication protocol for inter-service communication. Common protocols include HTTP, gRPC, and message brokers like RabbitMQ or Kafka. NestJS supports various communication strategies, allowing you to choose the one that best fits your needs. - Source: dev.to / 13 days ago

• Why Did Google Choose To Implement gRPC Using HTTP/2?

  gRPC is an open-source high-performance RPC framework developed by Google. The design goal of gRPC is to run in any environment, supporting pluggable load balancing, tracing, health checking, and authentication. It not only supports service calls within and across data centers but is also suitable for the last mile of distributed computing, connecting devices, mobile applications, and browsers to backend services.... - Source: dev.to / 27 days ago

• Difference between GraphQL, REST, and gRPC

  And, gRPC is a high-performance, open-source protocol used for creating APIs. It uses Google's Protocol Buffers as a data format and provides support for streaming and bi-directional communication. - Source: dev.to / about 1 month ago

• Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard

  gRPC, built on HTTP/2, inherently supports flow control. The server can push updates, but it must also respect flow control signals from the client, ensuring that it doesn't send data faster than what the client can handle. - Source: dev.to / 3 months ago

• Delving Deeper: Enriching Microservices with Golang with CloudWeGo

  While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / 4 months ago