AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
The Importance of Having an API for Postgres
A lot of times when you talk about API, you're sort of interchangeably with service. But the more I got thinking about it, the more it should be broken up by, what does the service need to do? And if it needs to touch Postgres and it needs touch elastic and it needs to Touch whatever else then it should be those should be available to that service because it knows how it needs to coordinate those various pieces of information. So for instance, there's a service that talks to elastic, there's another service that talks at SQL Server. You don't want all of your other APIs reinventing the wheel for like how they're going to connect to Postgres or manage