The architecture definition process that I use is called Assemblage. It uses the dark energy and dark matter forces to shape the architecture.
To learn more, please read this article:
https://t.co/W8MiP2QuKl
The essence of applying the Microservice architecture pattern is defining the service architecture: identifying the services, defining their responsibilities, their APIs and their collaborations (with other services).
A thoughtful and interesting AWS DynamoDb based option of the event persistency problem.
For Azure alternative, Cosmos DB + Change Feed processor https://t.co/hMzwf3jZ8o comes to mind.
As event-driven architecture continues to gain in popularity, I feel the need to remind folks about the risks of coupling caused by sharing raw business data via events, often occurring with noun-oriented services (like User, Product, Order, etc).
https://t.co/bR3kBM4FS7
Brand new blog post I wrote on 5 pitfalls that @WixEng engineers have encountered with event driven architecture.
Battle-tested proven solutions are provided for pitfalls around event sourcing, duplicate events, atomicity and more.
https://t.co/JKqpylkXzB
WTF is Command Event? When you only think in terms of events, everything gets shoved into that concept. Do you want to use Kafka or do you really need a message broker and queues?
https://t.co/ZCThglROiv
Business writing is a superpower.
But schools and employers do a horrible job teaching people to write.
In 1981, two advertising executives wrote a timeless guide for how to write in the business world.
And here are 12 of their tips you should staple to your desktop:
This Impact Map template shows (1) the difference between problem/strategic and solution/tactical design, and (2) most Scrum/Agile teams start at the right (tactical) rather than left (strategic) because stories are written before knowing the *why*.
#ImpactMapping#DDDesign
A new and super fresh addition to my collection of top content from @VaughnVernon and @tjaskula, looking forward to dig in! And of course looking forward to get it signed like the other two when the earth comes back into rotating and more planes to flying to Barcelona 😉
@VaughnVernon@tjaskula Received it yesterday off Amazon - I was surprised actually i got it so early! Inside it actually states Copyright Pearson 2022, so maybe it came to me from the future… but not a hologram 🙂
Thinking like a #cloud architect with four cloud #architecture tenets:
• Standardize to boost diversity
• Speed up to work differently
• Decompose to gain a broader view
• Automate to compose
Video now available on demand: https://t.co/aWFqddsrU3
new post: many people struggle with how to handle regulatory controls in a devops environment. Carl Nygard illustrates four patterns to consider.
https://t.co/gz3ZxeWUxB
Transformative IT needs to build streaming, not CDs. Don't make digital copies. Make something that could never have existed without digital technology.
This is one of my favourite slides when I talk about #microfrontends
Not only because I believe it’s fundamentally true also because we often forget about the context we operate in.
T. Sowell was used to say:
“There are no solutions; there are only trade-offs”
#tech#javascript