Service

One of the constant challenges for enterprise-architecture – probably all forms of architecture, in fact – is explaining the value of what we do. For example, like a good conference-organiser or event-host, often the better we do our work, the…

It was my grandmother’s 80th birthday. My parents wanted to make it a special occasion for her and for the family, so they booked us in for a meal at a place called Le Talbooth – then, as now, a decidedly…

Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – they either don’t work at all, or they serve someone else’s needs. Or desires. Or something of that kind, anyway. And therein lie a huge range of…

Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – they either don’t work at all, or they serve someone else’s needs. Or desires. Or something of that kind, anyway. And therein lie a huge range of…

Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – they either don’t work at all, or they serve someone else’s needs. Or desires. Or something of that kind, anyway. And therein lie…

Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – they either don’t work at all, or they serve someone else’s needs. Or desires. Or something of that kind, anyway. And therein lie…

Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – they either don’t work at all, or they serve someone else’s needs. Or desires. Or something of that kind, anyway. And therein lie…

Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – they either don’t work at all, or they serve someone else’s needs. Or desires. Or something of that kind, anyway. And therein lie…

Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t. And therein lie a huge range of problems for enterprise-architects and many, many others… This is the third part of what should be a six-part series…

Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – sometimes through incompetence or failure in operation, sometimes through incompetence in service-design, and sometimes even by intent. And therein lie a huge range of problems…

Services serve: they serve the needs of someone, or, in a broader ecosystem, the needs of something. Services serve – that’s why they’re called ‘services’. Yet what do we call something that purports to serve some need, but doesn’t? I’d suggest…

Private Database Cloud Services or Database as a Service (DBaaS) is no longer a new idea. In fact, it is quickly becoming the de facto standard for development and testing environments both on premises and in the public cloud. And while there are many use cases and deployment options, overall database total cost of ownership and business agility have benefited from a standardized approach to workload management. Whether you are a DBA, an operations manager, or a CIO, you are well aware that business-driven interest in social, mobile, big data, and internet of things have caused an explosion of development, data, and database workloads. The justification for database operations to pool resources and standardize services has never been clearer – watch this customer story (TRT1:30).