Running Microservices with Cloud Foundry and AWS

Editor's Notes

• #5: Out of the box onlineshop for SME. While others still tell us that amazon is going to be bancrupt soon anyway.
• #6: Message: Plattform (you may know) vs. yaas, I will talk about today
• #7: KEY MESSAGE Answer the question “What the hack is YAAS?” – This is our vision statement for YaaS since the early days! PUBLIC CLOUD There is no focus on delivery YAAS as a OnPremise solution. We are focusing on delivery a true public cloud platform which is delivered by our teams in a you build it you run manner. EVERYONE We want to address also new „customer groups“ with YAAS. So we want to be attractive for small agencies for smaller commerce projects. We want to be an attractive platform for freelancers and talented developers to offer their own packages and especially we want to offer our partners a place to productize their knowledge! EASILY DEVELOPER By offering tooling to speed up the development of solutions / packages for YAAS. EASILY EXTEND By offering concepts / hookins to extend solutions in a cloud compatible way: Events via Pubsub Hub and Mixins for Data Model extensions. EASILY SELL By offering build in metering, security, rate plans… PACKAGES AND APPLICATIONS Packages (Services & Builder Modules) and SaaS Applications LOW TOUCH MODEL The subscription process should be completely digital without any manual steps (-> everyone).
• #8: TIME: 120s KEY MESSAGE Understand our key goals when we started YAAS almost two years ago. (And the official name ;)) Cloud Capabilities Elastic scaling of independent components, stateless, zero downtime, usage based pricing, ... Independent / Daily Release A technical and a process problem. We wanted to tackel both in order to be able to release features continously once they are ready. Open for everyone Everyone should be able to just start playing around with YAAS and try it out. If you are developer you must be able to access all the needed information to get going and start developing / mashing up new solutions and in the end offer them to the world. On the other side we wanted to be open for everyone in a sense that you can use the technology you are most familar and wanted to prevent as much as possible force you to use a specific technology / language. There are just a few common requirements: RESTful APIs, a language agnostic API definition which emphasises on pattern reuse and sdks as starting points in the most popular technologies (angular / bootstrap, java sdk, ....) Innovation Platform Based on being an open technology platform and also making it as easy as possible to consume and sell packages we wanted to create an environment which is as flexible as possible and therefore should be perfectly suited to create innovative solutions. Digital Sales Channel for US and Partners Allow everyone to offer their own services apis / ui on the marketplace....
• #9: GAMES ARE FUN. EVERYONE IS PLAYING SOME. JUST AN EXAMPLE, REALLY.
• #10: COULD BE TALKING ABOUT IOT, SMART DEVICES – SAME THING REALLY
• #13: WHO: Andreas KEY MESSAGE Which technical solutions did we find to enable us to reach our goals described before? These three are the most influential ones in combination of open source implementation of specific problems. MICROSERVICES (http://martinfowler.com/articles/microservices.html) Small services with clear responsibility and minimal dependencies Independent release cycles between services / Componentization through Services Choose the best solution for the “problem” REACTIVE MANIFESTO (http://www.reactivemanifesto.org/) Message Driven; Non-Blocking / Async Request Processing Resilient: Communication Principals like Circuit Breaker 12 FACTORS (http://12factor.net) Stateless Services (share-nothing, horizontally partitionable nature of twelve-factor) Backing Services (Treat backing services as attached resources) Dependencies (Explicitly declare and isolate dependencies)
• #14: We absorbed agile & lean theories, reactive manifesto + 12 factors, good practices on API design, and combined them into our y-factors: https://devportal.yaas.io/overview/yfactors/index.html And we take great care that those principles and values are known and understood. We have posters and flyers in all the offices, promote them in lunch talks, etc.
• #15: WHO: Andreas KEY MESSAGE
• #16: WHO: Andreas KEY MESSAGE Just to illustrated how the high level architecture looks with the mentioned components put in….. Backing Services & Cloudfoundry run on the IAAS Layer. Our main building block (DevPortal, Market, Community, Builder) and OUR packages are running on the PAAS Layer.
• #19: WHO: Andreas KEY MESSAGE Which technical solutions did we find to enable us to reach our goals described before? These three are the most influential ones in combination of open source implementation of specific problems. MICROSERVICES (http://martinfowler.com/articles/microservices.html) Small services with clear responsibility and minimal dependencies Independent release cycles between services / Componentization through Services Choose the best solution for the “problem” REACTIVE MANIFESTO (http://www.reactivemanifesto.org/) Message Driven; Non-Blocking / Async Request Processing Resilient: Communication Principals like Circuit Breaker 12 FACTORS (http://12factor.net) Stateless Services (share-nothing, horizontally partitionable nature of twelve-factor) Backing Services (Treat backing services as attached resources) Dependencies (Explicitly declare and isolate dependencies)
• #20: Keymessage: Different requirements on Monitzoring and alerting Business / Manager: Overview, Usage, Conversion rate, etc. pp Service Dev: Responsetimes, Response Codes, Bottlenecks, service calls Plattform Operator: Close to Dev but different. He is responsible for Blackboxes, Ratios between different metrics, custom rules etc.
• #27: WHO: Andreas KEY MESSAGE Which technical solutions did we find to enable us to reach our goals described before? These three are the most influential ones in combination of open source implementation of specific problems. MICROSERVICES (http://martinfowler.com/articles/microservices.html) Small services with clear responsibility and minimal dependencies Independent release cycles between services / Componentization through Services Choose the best solution for the “problem” REACTIVE MANIFESTO (http://www.reactivemanifesto.org/) Message Driven; Non-Blocking / Async Request Processing Resilient: Communication Principals like Circuit Breaker 12 FACTORS (http://12factor.net) Stateless Services (share-nothing, horizontally partitionable nature of twelve-factor) Backing Services (Treat backing services as attached resources) Dependencies (Explicitly declare and isolate dependencies)
• #33: -