• Why should we care about architecture?/Are we getting code reviews wrong?

    Join us from 6pm on Tuesday September 17th at 1 New York Street, Manchester. ECOM are kindly hosting us in their event space and are also providing pizza, beer, soft drinks and more. As always this will be a group discussion. So please come and join in. continuing the theme of split sessions we have two topics - Why should we care about architecture? Which will involving answering - - Is architecture dead? Should all architecture emerge? - Why should people care about architecture? - How do we encourage people to care about architecture? Are we getting code reviews wrong? Where we will explore - - What does a good code review look like? - Are code reviews an effective quality gate? - Can code reviews help to measure architectural quality?

    1
  • Architecture Surgery (continued) & How to Learn Architecture

    This month will be a meet-up of two halves. We had so many great discussion points from last month's Architecture Surgery that we didn't manage to get through them all. So this month we'll continue where we left off and spend the first half talking through the most popular - prepare to place your votes on arrival: - How do people develop cloud services? Emulators vs dev in the cloud - How big is a Microservice? - Microservices and Serverless - friends or enemies - Have you escaped from the Angular JS trap? How can you upgrade/migrate - What are the benefits and biggest challenges of a multicloud architecture? - What are people using to run docker in production? In the second half, we'll discuss learning architecture. Where should you start? What resources have helped you? What have you found valuable? What should we avoid? Join us from 6pm on Tuesday August 20th at 1 New York Street, Manchester. ECOM are kindly hosting us in their event space and are also providing pizza, beer, soft drinks and more.

    19
  • Architecture Surgery

    ECOM

    Join us from 6pm on Tuesday July 16th at 1 New York Street, Manchester. ECOM are kindly hosting us in their event space and are also providing pizza, beer, soft drinks and more. This session will be a little different to others. It is your chance to bring along a question/discussion for the group. The meetup attracts a strong group of senior developers, technical/solutions architects, product owners, engineering managers. This is your chance to ask others for advice on how to tackle a problem whether that is technical or not. That could be - - We are thinking of using technology X? I'd like to gather other peoples feedback on it? - We need to secure our AWS EC2s but it needs to integrate OAuth2 what's best to use? - Our team keeps getting slowed down by support tickets. How do people manage the balance? - We have a big monolithic service with a large team working on it. How is best to start breaking it apart? Each question will be afforded a 10 minute slot (more if time permits). **Please post your questions below or send them to me in a message to book a slot**

    8
  • Architecting for Agile Teams - what is "just enough"?

    Too much up-front planning and commitment can stifle creativity and reduce our ability to respond to change. Too much agility can be chaos. On the scale between anarchy and autocracy, where is the sweet spot of "just enough" architecture? Join us from 6pm on Wednesday June 19th at 1 New York Street, Manchester. ECOM are kindly hosting us in their event space and are also providing pizza, beer, soft drinks and more. As always this will be a group discussion, so please come and join in. Please note the change to Wednesday - normal service (3rd Tuesday of the month) resumes in July.

    9
  • What techniques and tools do you use to communicate architectural decisions?

    Software development is as much about communication as it is technology. For architecture to be a success, communicating effectively with our teams and stakeholders is essential. This can seem straightforward at the outset, but as requirements change, teams churn and context gets lost, how can we ensure that our architecture remains on track? From oral histories and whiteboard sketches, through lightweight documentation to more traditional software architecture description documents - what tools and techniques really work? Join us from 6pm on Tuesday May 21st at 1 New York Street, Manchester. ECOM are kindly hosting us in their event space and are also providing pizza, beer, soft drinks and more. As always this will be a group discussion. So please come and join in.

    8
  • Which Javascript Framework should I choose?

    There is no shortage of Javscript frameworks in use today - Vue, Angular, React, Ember, Aurelia, Backbone, Polymer, Preact There is also plenty of stats about the usage of Javascript frameworks available online but in this session I want to dig a little deeper. We will discuss which frameworks people have used and how they have found them - What frameworks do people use? What do they like or hate about them? Any limitations? Would you use it again? What tooling do you use alongside (testing frameworks, task runners, transpilers, etc...)? As always this will be a group discussion. So please come and join us from 6pm on Tuesday April 16th at 1 New York Street, Manchester. ECOM are kindly hosting us in their event space and are also providing pizza, beer, soft drinks and more.

    3
  • Subject TBC

    ECOM

    1
  • Is avoiding Cloud lock-in worth the effort?

    Have you ever heard someone say - "If you use that Azure specific feature/service we won't be able to migrate to AWS if needed". A lot is said about trying to avoid being tied to a single cloud provider. But if you try to only use features common don't you lose some of the power of that provider? Tools existing which abstract the provider and deployment away. Do these work? What complexity do they add? Some advocate for a polycloud (using many providers) solution but doesn't that add more complexity and overhead. How do you decide what's best? Come join us we try to get to the bottom of some of this from 6pm on Tuesday February 19th at 1 New York Street, Manchester. ECOM are kindly hosting us in their event space and are also providing pizza, beer, soft drinks and more. As always this will be a group discussion. So please come and join in. This month we'll be discussing questions like:

    7
  • Breaking up the Monolith - Part Two

    ECOM

    At November's meet-up we discussed our experiences of migrating monolithic systems to microservices. We had some great conversation but one thing that was clear - we needed more time. So to start 2019 we'll be picking up where we left off and jumping back into Breaking up with Monolith. So once again, please come armed with your stories. Have you seen the benefits you expected? Has the cost of change been reduced? Have you encountered new problems? What would you do differently next time? What questions do you have for the group that we didn't get to discuss last time? As always this will be a group discussion, so please come and join in. This month we'll be hoping to discuss things like: - Microservice trade-offs - Testing strategies in a microservices architecture - Dealing with operational complexity - Handling cross-cutting changes Join us from 6pm on Tuesday January 15th at 1 New York Street, Manchester. ECOM are kindly hosting us in their event space and are also providing pizza, beer, soft drinks and more.

    4
  • ArchMCR Xmas Social

    SEVEN BRO7HERS BEERHOUSE

    For December we are going to skip the usual discussion and stick to the socialising. We are going to take over a corner of the Seven Brothers beerhouse in Ancoats. FREE BEER - ECOM have kindly offered to sponsor the event and put some money behind the bar so there will be some free drinks (it doesn't have to be beer). https://www.interquestgroup.com/specialisms/ecom We will be starting about 5ish so come down and join us for a drink.