People are often unaware that microservices really need to be independent. For example, you often see that all kinds of services are being made but that one database is shared. Another problem is that people program what they were used to doing in a monolith, making the chain of synchronous calls between services (over the network !!!) much too long. Neither is attention paid to spaghetti structure that can arise from all kinds of services that use each other and services are tightly coupled. … [Read more...] about How to avoid turning microservices into distributed spaghetti code
David may no longer have the amulet, but he has memories of the competition. "The map we produced was enormous. About 8ft by 6ft I would estimate. We realised that the Sabre Wulf maze was made up of a number of repeated segments, so we drew out the individual sections, photocopied them - yes, in black and white - and then hand coloured each one before tiling it all together like a huge wall-hanging mosaic. I hadn't thought about the amulet for well over 30 years until the other day when it popped into my head while discussing 80s culture with a colleague. It's so strange that it came up in conversation a few days before you contacted me. If it hadn't I probably wouldn't have even spotted your email. It obviously wants to be found." … [Read more...] about The seven treasures of Ultimate Play the Game
IT professionals and business leaders with an interest in cloud services have probably heard the term 'microservices', quite possibly in discussions about service-oriented architecture (SOA). There are good reasons why these evolving cloud technologies are popular: Both can make an organization and its cloud-hosted applications more agile, less likely to suffer outages, faster to update, and eliminate other problems associated with monolithic architecture and software. … [Read more...] about SOA versus microservices: How are they different?