2 ms·

Yes, but instead of making it a whole new service, you are probably already using a database and can use that service for this functionality as well. But since

Yes, but instead of making it a whole new service, you are probably already using a database and can use that service for this functionality as well. But since asking the question I've realized that if your application already needs a huge amount of servers because it simply gets that much traffic, then putting something like this in its own docker instance is probably the simplest way (it might even use postgres inside it), if those boundaries change now and then. But most companies aren't near that scale.

user5994461 10y ago
You're both missing the point here. Both things are conceptually equivalent: - Select(db, somekey, someparameters) [return some db object] - http_get_query(http://service.com/somekey/someparameters http://service.com/somekey/someparameters [return some JSON] They are external (micro)service: - they both need the target system to be available. - they both may fail in weird and unexpected ways. - they both need to handle failure gracefully. Their usage have different properties: - A database call need to have a permanent connection pool to the database, usually requiring db user and password. - A http call is just call and forget. It's a lot easier to use, in any applications, at any time.