Wise

Website

wise.com

$ Details

-

Categories

#Online Payments #Money Transfer #International Money Transfers #Currency Exchange

Startup details

Country

United Kingdom

gRPC

Website

grpc.io

$ Details

Categories

#Web Servers #Web And Application Servers #Developer Tools #Load Balancer / Reverse Proxy

Wise features and specs

• Low Fees
  Wise offers competitive and transparent fees compared to traditional banks and many other money transfer services.
• Real Exchange Rates
  Wise uses the mid-market exchange rate, meaning users get the real exchange rate without any hidden markups.
• Fast Transfers
  Many transfers through Wise are processed quickly, often within a few hours or a day, depending on the destination country and payment method.
• Multi-Currency Accounts
  Users can hold and manage money in multiple currencies with Wise's Borderless Account, making it easier for those who deal with international payments regularly.
• Transparent Pricing
  Wise is upfront about their fees and the total cost of a transfer, so users know exactly how much they'll pay and how much the recipient will receive.
• User-Friendly Interface
  Wise offers a clean and intuitive application and web interface, making it easy for users to navigate and complete transactions.

Possible disadvantages of Wise

• Limited Customer Support
  Wise's customer support is primarily online, and some users report difficulties in reaching live assistance or having slow response times.
• Transfer Limits
  There are limits on how much money can be transferred in a single transaction or over a period of time, which might be restrictive for some users.
• Lack of Physical Locations
  Unlike traditional banks, Wise doesn't have physical branches, which can be an inconvenience for those who prefer in-person banking services.
• Verification Process
  New users or those making large transfers may have to go through a lengthy verification process, which can delay the initial transaction.
• Not Available in All Countries
  Wise does not operate in every country, limiting its accessibility for some users looking to send or receive international payments.
• Occasional Delays
  While generally fast, some transfers may experience delays due to various factors, such as banking hours, holiday schedules, or compliance checks.

gRPC features and specs

• Performance
  gRPC uses Protocol Buffers, which are more efficient in terms of serialization and deserialization compared to text-based formats like JSON. This leads to lower CPU usage and faster transmission, making it suitable for high-performance applications.
• Bi-directional Streaming
  gRPC supports bi-directional streaming, enabling both client and server to send a series of messages through a single connection. This is particularly useful for real-time communication applications.
• Strongly Typed APIs
  gRPC uses Protocol Buffers for defining service methods and message types, providing a strong type system that can catch potential issues at compile-time rather than runtime.
• Cross-language Support
  gRPC supports a wide range of programming languages, including but not limited to Java, C++, Python, Go, and C#. This allows for flexible integration in polyglot environments.
• Built-in Deadlines/Timeouts
  gRPC natively supports deadlines and timeouts to help manage long-running calls and avoid indefinite blocking, improving robustness and reliability.
• Automatic Code Generation
  gRPC provides tools for automatic code generation from .proto files, reducing boilerplate code and speeding up the development process.

Possible disadvantages of gRPC

• Learning Curve
  The complexity of gRPC and Protocol Buffers may present a steep learning curve for developers who are not familiar with these technologies.
• Limited Browser Support
  gRPC was not originally designed with browser support in mind, making it challenging to directly call gRPC services from web applications without additional tools like gRPC-Web.
• Verbose Configuration
  Setting up gRPC and defining .proto files can be more verbose compared to simpler RESTful APIs, which might be a deterrent for smaller projects.
• HTTP/2 Requirement
  gRPC relies on HTTP/2 for transport, which can be problematic in environments where HTTP/2 is not supported or requires additional configuration.
• Limited Monitoring and Debugging Tools
  Compared to REST, there are fewer tools available for monitoring, debugging, and testing gRPC services, which might complicate troubleshooting and performance tuning.
• Protobuf Ecosystem Requirement
  Depending on the language, integrating Protocol Buffers might require additional dependencies and tooling, which could add to the maintenance overhead.

Analysis of Wise

TransferWise Review - 3 Must Knows (2020)

More videos:

gRPC, Protobufs and Go... OH MY! An introduction to building client/server systems with gRPC

More videos: