Skip to main content

Object orientation and Service orientation

Object orientation is all about modeling the real world information mainly through encapsulation, abstraction, polymorphism, containment, inheritance and so on. In simple words, an object contains the data structures and methods to change the content state. A typical OO run-time manages the life cycle of objects. You can create as many objects as required as long as the run-time does not over run its memory.

Service orientation requires you to encapsulate a process. The operations of a services are interaction points with the particular process. Data structures are the arguments for these operations. Service run-time shall validate the correctness of the process. Service can have multiple invocation instances, not multiple instances of service itself.

Example: TrainTicketBookingService involves a process.
- Check the train timings //  interaction point
- Check the seat availability // interaction point
- Issue ticket // interaction point
There could be many ticket counters that provide this service, but as a service, TrainTicketBookingService is the only service.

It is possible to design service oriented architecture through well defined process with object orientation. However, we always need to keep in mind, our goal is the service implementation, not to expose object interactions.

Comments

Post a Comment

Thanks for your comments.

Popular posts from this blog

Essential GCP services for a new age application

Identity and resource management IAM  Identity aware proxy Resource Manager Stackdriver Monitoring Stackdriver Monitoring: Infrastructure and application monitoring Stackdriver Logging: Centralized logging Stackdriver Error Reporting: Application error reporting Stackdriver Trace: Application performance insights (latency) Stackdriver Debugger: Live production debugging Development management Cloud Deployment Manager: Templated Infrastructure deployment Cloud Console: Web based management console Cloud shell: Browser based terminal/CLI Development tools Cloud SDK: CLI for GCP Container registry: Private container registry Container builder: Build/Package container artifacts Cloud source repository: Hosted private git repository Database services Cloud SQL: Managed MySQL and PostgreSQL Cloud BigTable: HBase compatible non-relational DB Cloud Datastore: Horizontally scalable non-relational (ACID) Cloud Spanner: Horizontally scalable relation...
Post a Comment
Read more

Cloud Architecture consideration

Thorough understanding of cloud architecture and Google technology Understand business objectives; Strategize cloud solution design inline with archtiecture best practices Design and Develop Manage robust, secure, scalable, highly available and dynamic solutions Proficient with multi-tiered distributed application - multi-cloud and hybrid environments Designing and Planning a cloud solution architecture - Business use cses - Product strategy - Cost optimization - Supporting application design - Data movement - Trade-offs - Build, buy or modify decisions - KPI and ROI metrics - Compliance and observability - HA and fail-over design - Elasticity - Scalability to meet growth requirements - Network integrations - Native networking - VPC peering, firewalls, container networking - Identifying data processing pipeline - Matching characteristics of storage systems - Data flow diagrams - Storage system structure - Mapping compute needs to platform products - License map...
Post a Comment
Read more

GCP - BigQuery Roles

GCP BigQuery Roles (Quick view)
Post a Comment
Read more