Maintenance model for external artifacts

When we think about maintaining a software solution holistically, we have to think about things like non-code change control and configuration management, in addition to the actual source code. For example, for maintaining a large web application, tracing:

admin-over-clients application

I have the same web application running on several different servers.
Now I want a central place to administer everything in one web interface. What is the best way to do this?

Entity Framework with large systems – how to divide models?

I’m working with a SQL Server database with 1000+ tables, another few hundred views, and several thousand stored procedures. We are looking to start using Entity Framework for our newer projects, and we are working on our strategy for doing so. The thing I’m hung up on is how best to split the tables into different models (EDMX or DbContext if we go code first). I can think of a few strategies right off the bat:

Should I use a workflow engine?

I need to add some new features to a PHP application. It is to follow the steps of a order. A process create some orders, the order goes to confirmation, then if approved is sent to a provider, later the provider confirm that can deliver the order, a request is made to the provider and so on…

What are options for 3rd Party Centralized Software Settings Management?

I am an architect in an enterprise looking to build a SaaS solution. Our products are distributed over many different deployable containers, Web Services, Web UI’s, etc.

Should business services cross bounded contexts?

Firstly, I am following the convention that a bounded context is synonymous to a department, or possibly one department has 1 to many bounded contexts.

Is SOA an Utopia? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]

Project/DLL separation of concerns in ASP.NET MVC

I’m coming from a web forms n-tier background into ASP.NET MVC projects, and I’m wondering what the best practices are for separation of the components of MVC into different libraries (or not to) in the way one might with an n-tier model. Most of the sample apps I have seen only had one project file and objects were separated only by folder.

Architecture advice for converting biz app from old school to new school?

I’ve got a WinForms business application that evolved over the past few years. It’s forms over data with a number custom UI experiences taylored to the business, so I don’t think it’s a candidate to port to something like SharePoint or re-write in LightSwitch (at least not without significant investment).

Inventory Consignment Flow

Not sure whether this is the right place to ask this question, but here goes..