awaneeshp wrote
Thanks for your valuable comments.
The scenario is as follows:
We are in the process of designing a portal which will act as a booking engine for air tickets. Now there are two cases either a user go to the site, books a ticket (using a booking module) which is available in our database or he can make bookings for the tickets available through some external interfaces (which would be available to him after the search) to which we are going to connect using some APIs.
Internal... normal module (standard access), External... classic web services which leverage your existing business layer (module business layer) to get the correct data.
Now, we wanted to implement this scenario using discrete webservices to manage the interfacing with the external resources. So we are going to access the outside data but not going to provide our data to outsiders through some interfaces.
But, i m concerned with the performance & scalability issues while devloping webservices using DNN module as well as the dependency on the DNN if i don't do this way, considering its future development due to its open source nature.
Please suggest me to take this architectural decision.
Thanks,
-AP
Perfromance and scalabitlity... To say something is scalable and performant would mean you've compared it to some baseline and mesaured your expectations and thus made your decision based on numbers and not ideas.
That said, you need to first define non-functional requirements (number of external concurrent users, number of internal users, expected traffic, etc..) and then sit down with an architect and define the best strategy for your scenario.
To tell you anything else would be incorrect because it can go in either way.... I can be right or wrong, and my assumptions can drive you to make the wrong decision.
(although based on my experience, you will likely be satisfied with the strategy mentioned in the begining of this post)