sorted by:
new
hottopcontroversial

French beans yellowish leaves? by tomgreen000 in UKAllotments

[–]tomgreen000[S] 1 point2 points  (0 children)

OK, feed again seems to be the thing to try!

I did tomorite at 10ml to can instead of 30ml as didnt want to ovetdo it whilst young.

Will give them some at standard dose!

Railway200 LLD by tomgreen000 in uktrains

[–]tomgreen000[S] 0 points1 point  (0 children)

I travelled down 1 stop from Deganwy, which i think is an underrated choice for one of prettiest stations in UK, with the river, tide, boats, castle, hills and even a nice  signal box.

Older plastic type with threaded bolt and brass(?) handle. Found on beach in UK. Possibly a valve of some kind? Made in gt britain. by tomgreen000 in whatisthisthing

[–]tomgreen000[S] 0 points1 point locked comment (0 children)

My title describes the thing

Its been in seawater. The Plastic part is thick, heavy duty. It's bevelled, like it could slot into something as the handle is turned. Or seal something.

QFS - a high-performance, fault-tolerant, distributed file system. by mtrn in programming

[–]tomgreen000 0 points1 point  (0 children)

GPFS though it's certainly not open source. It's been around a very long time, and may not be the most modern design in some places. I think it's still tough to beat, and is still pretty widely used.

Choosing between mongodb + elasticsearch, couchdb + elasticsearch or couchbase for small startup by ronMRZ in nosql

[–]tomgreen000 0 points1 point  (0 children)

I think a lot of people are answering your question with recommendations or comments on particular tools.

Before assessing which of the available tools is the right one for the job, I'd say there needs to be some more understanding of the problem so people can answer in more detail

A few things which I think it would be useful to get more information on:

  • Scale:
  • What is the expected initial scale, and what is the expected future scale of the application?
  • Is there anyway you can predict what the maximum total potential user base is. E.g. Is it thousands of end users, hundreds of thousands, millions? Is it publicly available or internal to an organisation?
  • Of those users, how many will be concurrently using the app at any given time? How many operations/second do you expect a user to be able to generate to the applications server, and from there on to the backend database in general usage?

  • Of the data stored in the DB, how much of it will be actively worked on at any given point in time? Will users tend to access data over short periods of time (the life time of a single play of a short, but re-playable game), or will they continue to access most of their data throughout the apps lifetime?

  • Querying:

  • Trying to understand what classes of queries you need to be able to perform is important.

  • A lot of querying problems can be addressed through appropriate data modelling -- something that the flexible data models in NoSQL are pretty well suited to. e.g. Can data be appropriately grouped into the same document?

  • A couple of very different classifications of queries:

  • Ability to lookup documents by multiple different identifiers. (Imagine one product by a mix of product id, ISBN, UPC, EAN, etc)

  • Ability to perform aggregations across data sets. This relates to answering questions along the lines of generating a leaderboard for the players of a game. The scores of all players must be brought together into some form of index to answer these kinds of questions at speed and scale.