c# - Cinema Booking system Architecture -


i doing school project in c# have create system handling cinema bookings , reservations.

my question is; software architecture beneficial system that? thinking client/server architecture thin client, maintain concurrency , make sure connected clients have access same data @ times.

but went ahead , read service oriented architecture, , don't quite understand implies. also, of literature i've read far, gives me impression have make choice between layered architecture , client server architecture. don't understand why 2 can't implemented simultaneously?

soa means ill build system in manner it's composed decoupled services (components) interacting 1 another. in general means ill build bunch of "sub systems".

layered means ill build system in manner each layer interacts each other , can loosely or tight coupled. in general means ill build 1 system 3-layers (ui, business , persistence).

they not different types of same abstraction, in fact different beast , can mix both or create service layered application or layer bunch of services or services ui services , others db access services , arrange in way similar layer topology.

to you homework, think how distributed ill system. ill fancy home page can see movies schedule, choose sit , buy or more system used guy selling tickets.

the first more appropriate soa scenario while second can more handled 3 layers application.


Comments

Popular posts from this blog

apache - Remove .php and add trailing slash in url using htaccess not loading css -

javascript - jQuery show full size image on click -