Micro CPH is a 2-day single track conference taking place in Copenhagen on May 14-15. Join us for inspiring talks about microservices, distributed and event-driven architecture, and get insights into the operational side of developing, running, deploying and testing microservices.Buy tickets
As the CTO at Just Software, Susanne is responsible for the software development of JUST SOCIAL - providing apps for collaboration and communication in organizations. She has a background in computer sciences and experience in software development for more than 15 years.
Lightning talk: Microservices in the future
In the light of rapidly changing market requirements organizations must accelerate to excel in the market. A 4-years research (by Nicole Forsgren, Jez Humble and Gene Kim) has revealed that software delivery performance has a strong impact on profitability, productivity and market share of technology organizations. Loosely coupled architecture, such as promoted by microservices, and empowered teams are some of the capabilities to improve software delivery performance. After having already introduced microservices in a startup context I would like to share some thoughts what to do differently when introducing microservices next time in the future.
James has been working at ThoughtWorks for nearly a decade. He joined back in 2005 as a developer. He had about 8 years experience prior to that point but still remembers feeling like an imposter for the entire first year. Since then, he has learnt more than he ever thought possible about how to build software from some of the most genuine, enthusiastic people he has met.
These days James is primarily interested in building distributed systems using web technologies. He has been a keen observer (and participant) in the resurgence of interest in SOA and can often be found being a loud mouth at conferences, usually on some aspect of building microservices. He has also been known to give his opinions on lean software engineering, domain driven design, organisational design and innovation.
Oh, and Welsh rugby.
Abstract to be added
Programmer...Single mom...Passionate about life, distributed computing, SOA, messaging and rock climbing! Currently dev at @particularsw
Indu Alagarsamy has been programming for over 15 years. She is currently part of the development team at Particular Software, the makers of NServiceBus, practicing her passion. Indu is also passionate about diversity and inclusiveness in the tech industry. When not programming, she is either rock climbing in sunny Southern California or spending time with her kids and her ginormous chill dog!
Autonomy & Asynchrony: The key to designing reliable systems
Abstract to be added
Nick is a strategic technical leader at Navico. He has a passion for delighting users, creating business impacts, crafting quality software, and building world-class engineering teams. He is the co-author of two books: Patterns, Principles and Practices of Domain-Driven Design (Wrox) and Designing Autonomous Teams and Services (O'Reilly), and frequently blogs about technical leadership at ntcoding.co.uk.
Strategic Microservice Patterns
Everybody knows there are hundreds of technical patterns you can apply to microservices. Yet nobody knows about the hundreds of domain patterns you can apply to microservices. By aligning your microservices with your business domain, you create a software system which is easier to comprehend, easier to evolve, and easier to develop at speed because it reflects the business. Understanding domain patterns helps you align your microservices and your business domain.
Learn why it’s important not to confuse The Entity Lifecycle Pipeline and The Proposal Pipeline. Learn how to manage complexity, and politics, when your domain contains an Octopus Context. And learn about many other domain patterns including The Dogfood Context, The Engagement Context, and The Brain Context.
To create the best architecture you also need to understand the business model. By viewing your microservices as business capabilities aligned to domain patterns, you will be able to design the best architecture for your business and for the teams building your microservices.
Sneha Inguva is a software engineer on the networking team at DigitalOcean. She has previously worked on the internal tooling team, inspiring passion to investigate observability primitives for new products. In her spare time, she frequents international cat cafes and medium to tall-sized mountains.
Observability and Product Release: Building, Testing, and Shipping Networking Features at DigitalOcean
Monoliths to microservices, containerization, blackbox to whitebox monitoring. DigitalOcean has experienced a shift in how services are built and deployed in the last few years, and along with that has come an even more important need to leverage the pillars of observability. Though the focus is often on services already in production, within this talk, I will focus on nascent services. Namely, how can we leverage metrics, tracing, and logging to test, improve, and deploy new microservices?
Listeners will hear about specific cases of networking services rigorously tested and tuned via learnings from observability primitives. We will showcase instrumentation, key visualizations, and takeaways from our testing. Listeners will be able to hear about areas for improvement and find out how to use these learnings for their own releases.
Nic Jackson is a developer advocate at HashiCorp and the author of “Building Microservices in Go” a book which examines the best patterns and practices for building microservices with the Go programming language. Additionally, Nic is writing “Vault in Action” with his co-author Anubhav Mishra, a book which discusses operational and application security using the popular open source HashiCorp Vault, due to be published summer 2019
Has the service mesh killed the fat network client?
Microservice design is deliberately loosely coupled and decentralized, while you gain the benefit of high availability. One problem is that we need to implement particular network reliability patterns like Load Balancing, Circuit Breaking, Retries, and Timeouts, often as a “fat” network client in each service.
In this talk, we will take a look in depth at these network reliability patterns and the benefits they give our systems. We will also see how we can leverage the power of the service mesh with Envoy and Consul Connect to implement them without the need for shared libraries and code changes.
+10 more speakers to be announced
We are a team of 6 people all with a developer background who have been organizing various tech meetups and have been part of a number of conferences as speakers and co-organizers for 5+ years.
We have teamed up in order to spice up the Danish tech scene with quality content around software architecture - this time dedicated to the world of microservices and distributed architecture.
Conference Code of Conduct
All attendees, speakers, sponsors and volunteers at our conference are required to agree with the following code of conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to help ensure a safe environment for everybody.
You have our contact details in the emails we've sent and our twitter handles above.
The Quick Version
Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organisers.
The Less Quick Version
Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.
Participants asked to stop any harassing behavior are expected to comply immediately.
Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualised images, activities, or other material. Booth staff (including volunteers) should not use sexualised clothing/uniforms/costumes, or otherwise create a sexualised environment.
If a participant engages in harassing behavior, the conference organisers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. Conference staff can be identified as they'll be wearing branded clothing and/or badges.
Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
We expect participants to follow these rules at conference and workshop venues and conference-related social events.