Lewis Cowles
Jun 18 · 1 min read

This is a collection of advice which makes a lot of assumptions. It’s just been brought up at work as a reason to build a monolith.

I’m infuriated that things like CORS are put up as barriers when it’s very little maintenance or overhead.

The ServiceWorkers themselves will be much more work than these few line changes, but you’ve ignored their limitations and focused on easily solvable points.

You have a point RE: sub-domains for locale, I prefer a path-based, query string based or cookie based locale to sub-domain routing, but that has nothing to do with complexity, it’s just basic common sense that sub-domains should be for domain separated entities like payroll vs calendar, website vs stock-management.

All of this is to AVOID making a monolith which is hard to maintain and difficult to reason about quickly, and your advice is guiding people right back towards monoliths.

    Lewis Cowles

    Written by

    Digital Architect & Owner - http://www.codesign2.co.uk UK-based I.T. Consultancy.I make things happen and could probably help you deliver software & experiences

    Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
    Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
    Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade