AMIMOTO Design Pattern + Server-less Architecture

AMIMOTO Design Pattern + Server-less Architecture

On the service design of AMIMOTO,
we approach with an awareness of the following three points:
1. Automation: Automate drastically
2. CloudNative: Leverage managed services
3. MicroServices: Implement a functionality with loosely coupled
With these three points, we make everyone able to build environment, developing service and operating it easily.

Bdaf0b291f02fe64a02cdf592a8a0c8f?s=128

AMIMOTO

May 06, 2016
Tweet

Transcript

  1. 2.

    Summary 1. Automation: Automate drastically 2. CloudNative: Leverage managed services

    3. MicroServices: Implement a functionality with loosely coupled On the service design of AMIMOTO, 
 we approach with an awareness of the following three points: With these three points, we make everyone able to build environment, developing service and operating it easily.
  2. 4.

    Solution 1. Automation: Constructing the server using CloudFormation 2. Reducing

    costs: Using managed services like RDS, S3 and CloudFront 3. Extensions as micro service: Connect with RESTful API 
 and Architecture with Server-less
  3. 5.

    Solution 1. Automation: Constructing the server using CloudFormation 2. Reducing

    costs: Using managed services like RDS, S3 and CloudFront 3. Extensions as micro service: Connect with RESTful API 
 and Architecture with Server-less
  4. 9.

    Solution 1. Automation: Constructing the server using CloudFormation 2. Reducing

    costs: Using managed services like RDS, S3 and CloudFront 3. Extensions as micro service: Connect with RESTful API 
 and Architecture with Server-less
  5. 13.

    Solution 1. Automation: Constructing the server using CloudFormation 2. Reducing

    costs: Using managed services like RDS, S3 and CloudFront 3. Extensions as micro service: Connect with RESTful API 
 and Architecture with Server-less
  6. 15.

    Issues on development • Bloated source code • Bloated DB

    • DB is single point of failure, so Auto Scaling will be meaningless • Tightly coupled functions, the core and the theme 8PSE1SFTT$PSF 1MVHJO 1MVHJO 1MVHJO 1MVHJO 1MVHJO 1MVHJO 1MVHJO 1MVHJO 1MVHJO 1MVHJO 1MVHJO 1MVHJO
  7. 17.

    Microservices • Build a system by multiple components • Components

    also function asɹ independent systems • loosely coupled • Linking systems with Restful API
  8. 20.
  9. 33.
  10. 43.

    Solution 1. Automation: Constructing the server using CloudFormation 2. Reducing

    costs: Using managed services like RDS, S3 and CloudFront 3. Extensions as micro service: Connect with RESTful API 
 and Architecture with Server-less
  11. 45.

    AMAZON 
 lambda AMAZON 
 DynamoDB AMAZON 
 API Gateway

    Server-less Architecture: Adding visualisation feature
  12. 47.
  13. 49.
  14. 51.

    Mautic Pre-scheduled marketing and sales, repeat automatically running to save

    time the task to be performed. Also this tool to aggregate the important and useful information order to concentrate to the correct prospects the sales team at the right time to one place.
  15. 52.
  16. 53.
  17. 54.
  18. 55.
  19. 58.
  20. 59.

    WP Mautic Insert a tracking tag in the automatically, which

    embedded short code generated form in Mautic. https://wordpress.org/plugins/wp-mautic/
  21. 60.
  22. 61.
  23. 62.
  24. 63.

    Mauticommerce Sending the customer information purchased the goods in WooCommerce

    to Mautic https://wordpress.org/plugins/mauticommerce/
  25. 64.
  26. 66.

    CF7 Mautic Extention Store inputed informations with Contact Form 7,

    into the lead in Mautic https://wordpress.org/plugins/cf7-mautic-extention/
  27. 67.