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.

Transcript

1. AMIMOTO Design Pattern + Server-less Architecture @Amimoto_Ami amimoto-ami.com Service design on AMIMOTO and its approach
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.
3. Problem 1. Hand working 2. Increasing maintenance costs 3. Non-reusable resources
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
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
6. AMAZON CloudFormation Awesome JSON
7. JIN-KEI Simple Stack
8. https://github.com/megumiteam/amimoto-enterprise-cfn/blob/master/json/001-mod.json
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
10. AMAZON RDS Awesome Database
11. AMAZON S3 Awesome Storage
12. AMAZON CloudFront Awesome Cache
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
14. Usual development in WordPress 8PSE1SFTT
    $PSF
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
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
16. Solution The Idea: MicroService
17. Microservices • Build a system by multiple components • Components also function asɹ independent systems • loosely coupled • Linking systems with Restful API
18. 8PSE1SFTT
    $PSF $POOFDUPS
    1MVHJO "1* "1* "1*
    .JDSP4FSWJDF
    .JDSP4FSWJDF
    .JDSP4FSWJDF Prospective development in WordPress
19. Implementation 1
21. AMAZON 
 Elasticsearch Awesome Search
22. Click Elasticsearch Service
23. Let’s get started Amazon Elasticsearch Service
24. Create Elasticsearch
25. Configure Cluster
26. Configure Cluster
27. Make sure your settings and attach access policy
28. Select access policy template
29. Select Allow open access to the domain
30. Save attached access policy
31. Detail of Elasticsearch domain
 Save Endpoint to a text file, you’ll need it later
32. Architecture 8PSE1SFTT
    $PSF $POOFDUPS
    1MVHJO "1* ".";0/
    &MBTUJDTFBSDI
34. https://wordpress.org/plugins/elasticommerce-search-form/
35. Enable plugin: Elasticommerce Search Form
36. Set up Elasticommerce Services
37. Copy Endpoint from text file paste it to the text box
38. https://wordpress.org/plugins/elasticommerce-related-items/
39. Enable plugin: Elasticommerce Related Item
40. Click Elasticommerce Services
41. Set up Elasticommerce Related Item
42. DEMO http://ecdemo.amimoto-ami.com/product-category/sample?orderby=popularity
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
44. Solution MicroService only can do them
45. AMAZON 
 lambda AMAZON 
 DynamoDB AMAZON 
 API Gateway Server-less Architecture: Adding visualisation feature
46. Architecture 8PSE1SFTT
    $PSF $POOFDUPS
    1MVHJO "1* "1* "1* 'VMM
    UFYU
    TFBSDI $PMMFDU
    TVCTDSJQUJPO
    EBUB 7JTVBMJTF
    TVCTDSJQUJPO
    EBUB
48. 'VMM
    5FYU
    4FBSDI %BUB
    7JTVBMJTJOH %BUB
    $PMMFDUJPO
50. Implementation 2
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.
56. https://mautic.org/docs/en/index.html
57. Architecture 8PSE1SFTT
    $PSF $POOFDUPS
    1MVHJO "1* .BVUJD
59. WP Mautic Insert a tracking tag in the automatically, which embedded short code generated form in Mautic. https://wordpress.org/plugins/wp-mautic/
63. Mauticommerce Sending the customer information purchased the goods in WooCommerce to Mautic https://wordpress.org/plugins/mauticommerce/
65. https://github.com/megumiteam/mauticommerce/wiki/How-To-Create-Form
66. CF7 Mautic Extention Store inputed informations with Contact Form 7, into the lead in Mautic https://wordpress.org/plugins/cf7-mautic-extention/
68. https://megumi.mautic.com/s/dashboard http://ecdemo.amimoto-ami.com/ %&.0
69. http://amimoto-ami.com/slack/ Any questions are welcome:
70. @Amimoto_Ami amimoto-ami.com THANK YOU! AMIMOTO Design Pattern + Server-less Architecture Service design on AMIMOTO and its approach