Tag Info

New answers tagged

2

My company use this approach (we are a Java/Maven/Jenkins shop). We use a webclient-common library in 4 or so web clients, and a webserver-common library in 3 web server projects. Just what advantage a "cut and paste" approach would add to this is a mystery to me. As with using any common code, good release management and version tagging practices are ...


1

If done correctly, separating business concerns into different databases (or at least different schemas) is a virtue. Please see Martin Fowler's description of the CQRS Pattern: As our needs become more sophisticated we steadily move away from [treating an information system like a CRUD datastore]... The change that CQRS introduces is to split that ...


1

Its not an abuse if your organization demands it. If there are security concerns or architectural guidance/governance that dictates it then it is warranted. We went through this with a 3rd party audit a while back and one of the 3rd party audit concerns was that our service layer directly interacted with the database. We had a web application layer and ...


2

SOA has many advantages other than increasing efficiency over a raw database confection. The most important benefit is that it provides a layer of abstraction that can be used to allow an underlying database to evolve its design without the need to synchronise releases with all consumers of the data it stores (this is particularly important if the database ...


4

There are many factors about your application stack that may indicate or contra-indicate use of SOA, so it will be very hard to tell you if everything they are asking for is appropriate. I will say that I don't think you should specifically not use SOA just because the machines happen to be in the same data-center. What if you need to enforce a new ...


1

If I may rephrase your question, you are asking "what happens to my system if something breaks?" Well, the short answer is that your system no longer functions properly. This happens all the time in complex systems. The degree to which you experience degraded functionality will depend upon what broke and how important it is. For example, when the space ...


2

My instinct leans more toward a message driven/SOA model where individual components were responsible for a subset of data and any component that needs access to that data would go through the appropriate channel. We actually have something just like this where I work. Our company offers financial services, so the overwhelming majority of data we want ...


2

One hundred database tables is not a whole lot, once you consider ordinary data tables, lookup tables, many-to-many linking tables, OLAP, and so forth. Is an enterprise-wide data model truly feasible? It better be. How else are you going to maintain and extend it? Rather than think of an enterprise data model as a "big ball of mud," it's more useful ...


1

My question here is has anyone seen a truly enterprise-wide master data model implemented and consistently used for anything larger than 100 or so tables? Kind of. I've seen one implemented that defined the core list of products and configurations for the (~5k employee) company. It was used for sales, maintenance, engineering. The actual ...



Top 50 recent answers are included