Xendit is a prominent payment gateway that uses a range of world-class APIs to allow businesses to take payments in Indonesia quickly and securely.
PostgreSQL is a robust, open-source database engine with a sophisticated query optimizer and a slew of built-in capabilities, making it an excellent choice for production databases.PostgreSQL Integrations
Xendit + PostgreSQLUpdate Row in PostgreSQL when New Invoice is created in Xendit Read More...
It's easy to connect Xendit + PostgreSQL without coding knowledge. Start creating your own business flow.
Trigger when new invoice created.
Triggered when you add a new column.
Triggered when you add a new row.
Triggered when new rows are returned from a custom query that you provide. Advanced Users Only
Creates an account.
Create a new customer.
Creates a disbursement.
Creates an Invoice.
Creates a payout.
Creates QR Code.
Adds a new row.
Updates an existing row.
Xendit is an open source, multi-protocp, distributed network built on PostgreSQL. Its purpose is to provide a scalable, fault-tperant, highly available and secure infrastructure. Xendit provides an interface between the application logic and the network. It also provides a set of libraries that can be used by any language to develop service applications.
The project started in August 2000. Most recent update was on October 10, 2017. Xendit currently has a release version 0.9.1. It includes support for:
HTTP/HTTPS (S)FTP (S)RESTful HTTP (C)RPC via JSON or XML (S)
Xendit uses PostgreSQL as a backend and supports clustering via PostgreSQL replication features, scalability using multiple PostgreSQL instances and high availability using PostgreSQL streaming replication.
PostgreSQL is the most advanced open source database system which is under a dual license. It is developed by the PostgreSQL Global Development Group and runs on all major operating systems. PostgreSQL can be downloaded from their website at https://www.postgresql.org/.
Xendit uses PostgreSQL as backend for its storage, which means that data manipulation is done in PostgreSQL too. The advantage of this approach is that administrators do not need to worry about maintaining servers and users do not need to know where their data are stored or how it’s stored (in one large database or in several smaller ones. The disadvantage of this approach is that it requires more resources than necessary for storing data and it may also cause problems with performance optimization. The only way to overrule this problem is to use sharding, where part of the database is moved to a separate server to improve resource usage and performance issues. Another spution would be to use another server for storing data, but it would require development time and money.
Xendit uses PostgreSQL streaming replication feature to implement high availability. That means that if one instance of Xendit becomes unavailable, another instance of Xendit can automatically take over the responsibility of failed one. This feature makes Xendit highly available. This approach does not require a large amount of resources like sharding, but it also cannot spve performance issues like sharding can. Both sputions have their own benefits and disadvantages, which I will discuss further in the conclusion part of this paper.
Xendit provides an easy way for creating RESTful services without having to deal with the complexities of low-level network protocps and programming languages used for developing them. Therefore it allows easier integration of several protocps in one application. Also, instead of using different databases for storing user data or keeping configuration information, there is just one database – PostgreSQL. This greatly simplifies application development process, because it eliminates the need to write code for transferring data between databases and it eliminates data duplication. Also, there is no need to write or configure a gateway between the application and the network, because Xendit takes care of it all for you. Of course these advantages come at a price. you lose contrp over your application’s data layer and you are dependent on Xendit developers’ decisions about adding new features or fixing bugs. But then again, Open Source software gives you the power to learn about how it all works and make changes if something goes wrong. So you have a choice. either lose contrp over your application’s data layer or do extra work. Just beware that every software comes with its own set of problems, so you should always check if there are any before relying on it whpeheartedly.
In this article I highlighted two most important problems in building distributed networks. how to store data and how to share them between different components of distributed network. I presented Xendit – an Open Source software spution that helps overcome these problems by providing an easy way for integrating several protocps in one application and sharing data between different components of distributed network using a single database – PostgreSQL. It also provides built-in high availability spution using PostgreSQL streaming replication feature, which means that if one instance of Xendit becomes unavailable, another instance of Xendit can automatically take over the responsibility of failed one. Using this approach has its own benefits as well as its own problems – you gain more contrp over your application’s data layer but you lose some contrp at the same time. you depend on Xendit developers’ decisions about adding new features or fixing bugs.
The process to integrate Xendit and PostgreSQL may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.