Data service API design
We’re designing a data service that will store a large number of statistics about stocks, including historical data. The client will be a web application, which will need to pull various bits of data to show in different places on the site.
Advise on How To migrate a huge monolithic java application towards something service-oriented
I am confronted with the problem of migrating a huge monolithic java web application towards a more service oriented approach. The application has grown for years from what it was originally desinged for and is still growing. That means a lot of changed customer requriements where development under time pressure with few concernce about code quality. That led to very very complex code structure (no modular packaging, a lot of complex inheritants, mix of functionality in classes and as good as no documentation).
How essential is it to make a service layer?
I started building an app in 3 layers (DAL, BL, UI) [it mainly handles CRM, some sales reports and inventory].
Service Layer – how broad should it be, and should it also be used from the local application?
The background:
Motivation for a service layer (instead of just copying dlls)?
I’m creating an application which has 2 different UIs so I’m making it with a service layer which I understood is appropriate for such scenario.
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.
Service layer design
I am developing an MVC website in PHP, and for the first time, I would like to implement a service layer. I have some design considerations I would like to get some advice on. The backend will by no means be a large enterprise system, so I am looking to keep things relatively simple while still leveraging the benefits of a service layer.
Identifying Domain Services & Application Services when doing DDD
-I’m trying to figure out how to identify Application Services in my application. I think I can identify a Domain service by 2 things:
Is it a good idea to use a kitchen-sink server for various services?
My (new) development team is setting up its software development environment. I won’t describe the whole scenario, since that’s another, much-maligned question.
Is it a good idea to use a kitchen-sink server for various services?
My (new) development team is setting up its software development environment. I won’t describe the whole scenario, since that’s another, much-maligned question.