3 ms·
Sure, so there are a lot of projects like this that does the same for Redis: ServiceStack has http://www.servicestack.net/RedisAdminUI/Public/Metadata http://w
by mythz 16y ago
Sure, so there are a lot of projects like this that does the same for Redis:
ServiceStack has http://www.servicestack.net/RedisAdminUI/Public/Metadata http://www.servicestack.net/RedisAdminUI/Public/Metadata
Redis adapters for Nginx: http://wiki.nginx.org/HttpRedis http://wiki.nginx.org/HttpRedis and https://github.com/agentzh/redis2-nginx-module https://github.com/agentzh/redis2-nginx-module
Finally there is webdis https://github.com/nicolasff/webdis https://github.com/nicolasff/webdis which is standalone and includes its own web server
- dlsspy 16y agoNone of these things are similar to couchapp: * They all require two servers running (redis + a web server) * None provides a framework for building an application. * None provides n-way replication. * None provides offline support. I get that they do mean you can build a web app. The question above was why it would make sense to use couch instead of redis. The primary answer is because the database already does most of what you want (including serving the HTML to the web browser) since it speaks the same language as the eventual client.
- mythz 16y ago>They all require two servers running (redis + a web server) So? separating web service access to the datastore is simply separation of concerns and just good modular design. A redis hybrid solution is still going to be faster than Couch. >None provides a framework for building an application. There is lua scripting available in some of them and the application fx is generally on the client. >None provides n-way replication. Out-of-the-box Redis supports trivial (as many as slaves as you want) replication. >None provides offline support. eh? wtf?