Salesforce Integration: Context and Patterns

Integrating with Salesforce be in a Marketing or Customer management context is the norm these days. Salesforce offers a lot of flexibility for information exchange, storage and for capturing events on change This post lists the interaction patterns we observe with Salesforce, the usage contexts, issues and best-practise Salesforce Inbound Patterns How do we createContinue reading “Salesforce Integration: Context and Patterns”

APIs are an abstraction, all abstractions are leaky: Managing what you leak is key to a good API

Modern software is built over the network with systems hooked-up either privately within the internal enterprise eco-system or with a trusted partner or via a public channel Traditional system integration (ESB) engineers working within project directives would have delivered interfaces for system to system or partner to system integration while working closely with the consumingContinue reading “APIs are an abstraction, all abstractions are leaky: Managing what you leak is key to a good API”

How to pull a reverse-Conway to deliver Products vs Projects: Domain Centric Product Teams

Modern software engineering is oriented towards building networked distributed features for a highly connected and web savvy customer base in varying contexts. Traditional team structures within the enterprise have evolved from technical SME cliques as engineers who “Ate lunch together wrote Software together” Good product strategy requires thinking about product features are built by engineeringContinue reading “How to pull a reverse-Conway to deliver Products vs Projects: Domain Centric Product Teams”

Coupling across context boundaries: The API anti-pattern hurting your user experience

APIs can be used to query information or command changes in system of record. Even the most efficient & fast real-time web service still struggles with having to wait for an “ack” (acknowledgement) leading to coupling between the invoker & provider. If this happens within a cohesive business function then the coupling is necessary, howeverContinue reading “Coupling across context boundaries: The API anti-pattern hurting your user experience”

Observations in building Domain oriented services: How to think about building the right service for your enterprise

APIs are the abstractions over technical services. Good APIs mirror strategic thinking in an organisation and lead to better customer experience by enabling high-degree of connectivity via secure mechanisms Too much focus is on writing protocols & semantics with the desire to design good APIs and too little on business objectives. Not enough questions areContinue reading “Observations in building Domain oriented services: How to think about building the right service for your enterprise”

A Pandemic, Open APIs and Citizen Science: Its 2020 baby!

Human societies have been hit by pandemics through the ages and relied on the central governing authorities to manage the crisis and disseminate information. I believe this time around with COVID-19, our societies have access to more information from our governments because we have the internet If this pandemic is an evolutionary challenge, then ourContinue reading “A Pandemic, Open APIs and Citizen Science: Its 2020 baby!”

Microservices for orchestration: How to apply the stateful process adapter pattern

What are stateful microservices? Microservices holding state while performing some longer-than-normal execution time type tasks. They have the following characteristics They have an API to start a new instance and an API to read the current state of a given instance They orchestrate a bunch of actions that may be part of a single end-to-endContinue reading “Microservices for orchestration: How to apply the stateful process adapter pattern”

History of web services: Monolith to Microservices

If you have struggled with decisions when designing APIs or Microservices – it is best to take a step back and look at how we got here. It helps not only renew our appreciation for the rapid changes we have seen over the past 10-20 years but also puts into perspective why we do whatContinue reading “History of web services: Monolith to Microservices”

De-mystifying the Enterprise Application Integration (EAI) landscape: Actors, terminology, cadence and protocols

Any form of Enterprise Application Integration (EAI) [1] work for data synchronization,  digital transformation or customer self-service web implementation involves communication between the service providers and service consumers. A web of connections grows over time between systems, facilitated by tools specialising in “system-integration”; this article covers how the clients, services and integration tools communicate andContinue reading “De-mystifying the Enterprise Application Integration (EAI) landscape: Actors, terminology, cadence and protocols”

Tackling complexity: Using Process maps to improve visibility of integrated system features

“Entropy always increases “– second law of thermodynamics Enterprise systems are similar to isolated physical systems, where the entropy or hidden-information always increases. As the business grows, our technology footprint grows as new systems are implemented, new products and cross-functional features are imagined and an amazing network of integrations emerge Knowing how information flows andContinue reading “Tackling complexity: Using Process maps to improve visibility of integrated system features”