Swift Micro Services in Production

What are micro services, who is using them and why should you be thinking about using them?

Transcript

1. Swift Micro Services in Production By Ralph Küpper - CEO of Skelpo
2. Content • Background • Currently Trending Solutions • An alternative Approach • Micro Services and their Architecture • Use Cases & Examples • How to start? • Q&A
3. Background - Started programming at 8 yo - Started Skelpo with 14, incorporated with 17 - Weird mix between business and programming - German / Likes well engineered products - Built 5+ social networks Ralph Küpper Online: proggeramlug / amlug ralph@skelpo.com
4. Who has ever maintained a Wordpress site? (Or Magento, Shopware, OXID, Typo3, Drupal etc.)
5. What are the most common issues with these systems? • Plugin “Dependency Hell” • Scripting Attacks • Monolithic Complexity • Constant „important“ Updates • Overall slow
6. How about a different approach?
7. What is a Micro Service Architecture? Picture Source: https://medium.com/startlovingyourself/microservices-vs-monolithic-architecture-c8df91f16bb4
8. What is a Micro Service Architecture? Picture Source: AWS
9. What is a Micro Service? Picture Source: https://www.researchgate.net/figure/The-new-FX-Core-microservice-architecture-Red-services-are-infrastructure-services_fig2_316088971
10. A big application with many small pieces • Obvious Benefits: • Individual care for each service (different frameworks, languages, tools) • Separate teams & responsibilities • Individual approaches for each service (different databases, server setups)
11. Disadvantages to a Micro Service Architecture • No „quick & easy fix” setup. • Many moving parts, debugging can be quite painful. • Can require more developers than available. • Often more time-consuming and expensive.
12. Why Swift is particularly well suited for Micro Services • Easy language that is fun • Modern language with modern features • Frameworks that were built with specifically micro services in mind • Native Apps, fast performance • Strong Community
13. Ditching the off-the-shelf industry • Most projects start out with small requirements ... that grow bigger and bigger. • To a point where the original off-the-shelf solution often gets so customized with plugins ... • ... and themes .. • .. that it really is not off-the-shelf anymore.
14. Reinvent the wheel • Instead of using (your choice of off-the-shelf software) and modifying it to fit your needs .. • … build your own custom solution! • Use templates and ready-to-go services • Customize. • No plugins need. • Updates on demand.
15. Who is using a Micro Service Architecture? • Enterprise has been using micro services for years. Lufthansa, UPS etc. • Smaller companies and startups start to embrace it.
16. Use Cases Examples of Micro Service Applications
17. Fuelish Micro Service Use Case
18. Fuelish Feature: News & Stories Typical social media newsfeed Images, Videos & Text Comments & Likes
19. Fuelish Feature: News & Stories Micro Services: 1. User Manager 2. Content Manager 3. Group Service 4. Media Service 5. Comments & Likes Service
20. Fuelish Feature: Drive & Tours Users can create Tours Users can follow & participate Tours can be recorded through GPS
21. Fuelish Feature: Drive & Tours Micro Services: 1. User Manager 2. Group Service 3. Media Service 4. Comments & Likes Service
22. ReviewSender Micro Service Use Case
23. ReviewSender: A more complex application
24. ReviewSender: Review Management • One Micro Service is containing reviews • One Micro Service is aggregating reviews • One Micro Service is analyzing reviews • Different configs for all 3 services
25. How to start?
26. Skelpo Micro Services • User Service • Content Service (Blog posts, news, static content) • Product Service (Products & Service Offerings Management) • Comments Service (Customer Response) • Order Service (Billing) • and some more: https://github.com/skelpo/micro-services
27. Questions & Feedback
28. Thanks for listening!