architecture

问题 Are machine word size (or smaller) writes serialized? Only one native opcode is needed to copy register content to RAM. 回答1: Writing data to RAM is atomic. If two CPUs try to write to the same location at the same time, the memory controller will decide on some order for the writes. While one CPU is writing to memory, the other CPU will stall for as many cycles as necessary until the first write is completed; then it will overwrite its value. This is what's known as a race condition. Writes

问题 There are many, many examples in books, and on the internet about how to use Servlets as JSPs. But I would like to know what the best way to go about using them, with a mind to good architecture. Should there be a one-to-one relation of Servlets to JSPs? Acting like ASP.NET "Code-Behind" pages? Or more like ASP.NET MVC, with a single Servlet controlling multiple actions, and forwarding to multiple views? This is a question regarding pure Java EE development. Please don't simply suggest

问题 I have a general difference of opinion on an architectural design and even though stackoverflow should not be used to ask for opinions I would like to ask for pros and cons of both approaches that I will describe below: Details: - C# application - SQL Server database - Using Entity Framework - And we need to decide what objects we are going to use to store our information and use all throughout the application Scenario 1: We will use the Entity Framework entities to pass all around through

问题 I'm doing some architecture work on a new solution which will initially run in Windows Azure. However I'd like the solution (or at least the architecture/design) to be Cloud Agnostic (to whatever extent is realistic). Has anyone done any work on this front or seen any good white papers/blog posts? Our highlevel architecture will consist of a payload being sent to a web service (WCF for instance), this will be dumped on a queue (for arguments sake) and a worker process will grab messages off

问题 I'm trying to determine if it is possible (or practical) to implement Uncle Bob's Screaming Architecture in ASP.NET MVC 5 rather than using the default folder structure. Here's a link to a description of the Screaming Architecture: http://blog.8thlight.com/uncle-bob/2011/09/30/Screaming-Architecture.html A hypothetical folder structure would look something like this: Root Customers Controllers CustomerController.cs Models Customer.cs Views Index.cshtml Details.cshtml Update.cshtml Employees

问题 I am still trying to make sense of micro service architecture. The idea to separate different application (include the database) excites me. But I am still confused if there are two micro-services e.g. Product and User. both product and user own table product and user respectively in their database. According to best practice in micro service, we only can access the database from the service. The problem is, let us suppose we have product table that has user_id column. We want to do search

问题 I'm attempting to create a small demo web application that is loosely coupled, highly testable, has nice clean code, etc. In short, I'm experimenting with doing things the right way. ;) I currently have three projects in my Wolfie solution: Wolfie.Core - contains business entities Wolfie.Data - contains data access code, references Core. Wolfie.Web - will be a nancy web site. As it stands the Core knows nothing about any of the other projects. Data has to reference Core as Core has the types

问题 I am working on a web application which involves create list of Restaurants in various lists like "Joe's must visit places". Now for each Restaurant and list, I have display on website which calculates Calculating popularity of a Restaurant Popularity of a list Number of lists a Restaurant is present in Currently I am using MySQL statements in PHP for this but planning to switch to MySQL VIEWS and do a simple select statement in PHP... my question is, What is Advantage/Disadvantage of using

问题 Again - i'm confused about DDD things :) I have architeture (I'm still working on it) that in short hand looks like that: DataLayer: EntityDao -> Implementing domain layer interfaces (NHibernate) DomainLayer: EntityRepository -> Repository for each entity with injected Dao DomainObjects/Entitys -> Some logic UI ASP.Net MVC And I'm right now in that point where I feel to create and use some Service class. I have some questions with that: 1.Should I create at least one service for each entity

问题 I remember seeing a blog (or something) that said you should not use <% if ... %> in .aspx files in ASP.NET MVC, but I can't remember what it said the alternative is. Can anyone remember seeing this and point me to it? 回答1: I'm not sure if this is what you saw, but here is a blog that mentions it. See item #11. 回答2: Basically what it means is that you shouldn't have huge if statements in your Views, your Controllers and ViewModels should be able to handle the logic. Example: <h2 class="title"