3 ms·
Yes. No. Maybe. Really need more context to your question: certainly separation of duties can be a good protocol to follow ... but having everything in one p
by warrenm 9y ago
Yes.
No.
Maybe.
Really need more context to your question: certainly separation of duties can be a good protocol to follow ... but having everything in one place can be adequate, too.
Tiering your web and database into different servers, clusters, groups, etc can be smart - especially since you can focus on the resources which best optimize the given tier, and not have to worry about contention (and on services like DO, utilizing private networking so only your web server(s) talk to your db server(s) cuts down on your attack vectors.
Having services on different systems also allows for one (or more) to be down without impacting others (unless it's the db tier, and both mail & web rely on it ... then db being down affects everything).
- oblib 9y ago"on services like DO, utilizing private networking so only your web server(s) talk to your db server(s) cuts down on your attack vectors." Thank you for mentioning this. I was not aware DO provides tools for this so I'll be looking into that. Right now I'm using CouchDB CORS configuration to restrict access to the DB to only the app file server.
- warrenm 9y agoSpend some time on their docs and API references: there's a lot in there that could benefit you :)
- oblib 9y agoThere's still surprising little on installing and configuring CouchDB 2.0. there, but there is a lot of great info there and I've poured through a lot of it. I'll probably post my install instructions in the comments of their CouchDB 1.6 guide so others can help improve them soon. I've not yet had a chance to play with the DO API yet but I do want to, and will sometime soon.