406 reputation
1312
bio website
location
age
visits member for 1 year, 11 months
seen May 24 at 5:30

May
24
awarded  Citizen Patrol
May
24
comment Correct pattern for Worker Processes involving Queues & Tables
The "Table" will be used strictly for operational and logging data. Objects stored in the table can have different columns or schema but they are non-hierarchical. Do you think this separation of business data from operational data is appropriate and does it sound like it is appropriate to use a relational store for the business data and this other "table store" for the operational data? Thanks.
May
24
comment Correct pattern for Worker Processes involving Queues & Tables
The "Table" component in the sequence diagram is something in Azure called "Table Storage". Table storage is like a database table. It isn't a relational database. You can't have joins between tables. In fact, there will be a relational database in this pattern as well. It will hold the users and business data and such, and both the Worker and the Source will use this relational database.
May
24
awarded  Benefactor
May
24
comment Correct pattern for Worker Processes involving Queues & Tables
Thanks David! Great answer!! Part of what I am taking from your answer is that you didn't see anything glaringly defective about my design. Let me explain part of it in further detail and let me know what you think.
May
19
awarded  Promoter
May
17
revised Correct pattern for Worker Processes involving Queues & Tables
made it concrete with a specific example and included some of the quality attributes the design aims to acheive
May
16
asked Correct pattern for Worker Processes involving Queues & Tables
Apr
9
awarded  Famous Question
Mar
5
awarded  Popular Question
Nov
8
awarded  Peer Pressure
Sep
5
revised What are the most crucial categories of content to organize into an internal developer portal in a large company?
added 349 characters in body
Sep
5
asked What are the most crucial categories of content to organize into an internal developer portal in a large company?
Aug
16
awarded  Yearling
Apr
12
awarded  Notable Question
Feb
6
comment Why is NoSQL better for this scenario?
I'm starting to get it. Databases are often optional. In my scenario, I could potentially just store the JSON documents in a folder and name them by convention: <userID>_<type>. This document would contain the most recent data for that user of that type. I could then load and transform this data either on the server as part of the request handling, or, could even let JavaScript in the browser merge/sort/page/filter through the data. Why would I even need to use a NoSQL database or key/value store when I could just use the filenames to look up the data? Am I getting it? Thanks.
Feb
5
comment Why is NoSQL better for this scenario?
I guess we can just use JavaScript from the browser to loop through the friends, and then display/store results as we obtain them and persist them in some sort of session state? HTML 5 local storage?
Feb
5
comment Why is NoSQL better for this scenario?
Here's a problem with that: Facebook doesn't support obtaining all the data we are looking to assemble together about the user's friends in a single, high performing HTTP call. For example, if I want to just show the user a list of their friend's birthdays, I still have to loop through their friend's list and get each birthday separately. For more than a dozen friends this can take significantly longer than a request, it can even take up to 5, 10, 20 minutes! Also, when the user returns to our site we want to show the last data we acquired for them immediately.
Feb
5
answered How important is it to reduce the number of lines in code?
Feb
5
awarded  Critic