• The Microservices Meetup at River Island

    Talks by Resilient PLC, a communications company, on how they went from a Monolith into a distributed Cloud based Microservices system. How you go about breaking down massive systems? By empowering teams! Define what the goal is, whether it is automation, cloud or serverless and empower teams to execute their own initiatives to break down the monolith piece by piece.
    The road to cloud automation can be difficult, uprooting an existing system from onsite into the cloud can have its own series of teething pains. Maintaining service and encryption while going through new systems can be a challenge when first starting out, especially while maintaining a live product that has millions of users!
    Excellent communication is required between teams and disciplines so that developers, QAs, project managers etc maintain the product in prime condition while breaking it down piece by piece.

    Next up a talk on the failings of Microservices!
    Microservices require effective architecting to function well, else you fall into the trap of creating a distributed monolith. If all the parts of a microservices system rely on each other to function, then they are co-dependent and fall into this pitfall. This is an issue that can affect microservices as they grow older, if V2.0 relies on V1.0 in some part of the codebase it can become very difficult to untangle!
    The most important thing to take away is that microservices are not automatically better, they help with scalability issues and solve specific issues that monoliths have, but with the wrong design and architecture, they can make those problems far worse!


    Name:  DSC_0336-min.JPG
Views: 14
Size:  1.02 MB
    3
  • Talks by Resilient PLC, a communications company, on how they went from a Monolith into a distributed Cloud based Microservices system. How you go about breaking down massive systems? By empowering teams! Define what the goal is, whether it is automation, cloud or serverless and empower teams to execute their own initiatives to break down the monolith piece by piece.
    The road to cloud automation can be difficult, uprooting an existing system from onsite into the cloud can have its own series of teething pains. Maintaining service and encryption while going through new systems can be a challenge when first starting out, especially while maintaining a live product that has millions of users!
    Excellent communication is required between teams and disciplines so that developers, QAs, project managers etc maintain the product in prime condition while breaking it down piece by piece.

    Next up a talk on the failings of Microservices!
    Microservices require effective architecting to function well, else you fall into the trap of creating a distributed monolith. If all the parts of a microservices system rely on each other to function, then they are co-dependent and fall into this pitfall. This is an issue that can affect microservices as they grow older, if V2.0 relies on V1.0 in some part of the codebase it can become very difficult to untangle!
    The most important thing to take away is that microservices are not automatically better, they help with scalability issues and solve specific issues that monoliths have, but with the wrong design and architecture, they can make those problems far worse!


    Name:  DSC_0336-min.JPG
Views: 14
Size:  1.02 MB