How Much Architecture Is “Enough?”: Balancing the MVP and MVA Helps You Make Better Decisions
The Minimum Viable Architecture (MVA) is the architectural complement to a Minimum Viable Product (MVP).
Agility and Architecture: Balancing Minimum Viable Product and Minimum Viable ArchitectureInfoq
Adaptive Architecture: a Bridge between Fashion and TechnologyInfoq
Building Better Platforms with Empathy: Case Studies and Counter-ExamplesInfoq
Grab Redesigns Counter Service Storage for 50% Lower P99 LatencyInfoq
The Async Multiprocessing Has Sound Foundations in Linux, But Further Testing is NeededInfoq
AI Agents with Cloud Credentials Are Outrunning Billing Guardrails Built for Human-Speed MistakesInfoq
Calling Your Video Game With Your Phone: Part 1Deepgram
No Code Transcription: Simplifying Workflows with Deepgram and Make.comDeepgram
Plumsail Documents: Zapier spp spotlightZapier
7 ways to use Zapier's Zendesk integrationZapier
How automation helped us get better customer reviewsZapier
When CI Meets CD: Deliver With ConfidenceThenewstack
DevSecOps: Why Security Shouldn’t be Sacrificed for SpeedThenewstack
Three Key Design Considerations for an Event-Driven ArchitectureThenewstack
Transform and Future-Proof Your Architecture with MACHThenewstack
Oso Unbundles Security AuthorizationThenewstack
Introducing CORPS: The 5 Pillars for a Robust Cloud Architecture FrameworkThenewstack
What is a Streaming Multiprocessor Architecture?Modal
Position Sticky and Table HeadersCss Tricks
Pseudo-Randomly Adding Illustrations with CSS | CSS-TricksCss Tricks
