Progress the system operation drastically with Cloud Automator — AMIMOTO side—

Transcript

1. Progress the system operation drastically with Cloud Automator — AMIMOTO

   side— @Amimoto_Ami amimoto-ami.com The service design concept of Amimoto and its underlying thought

2. WordPress users should want to focus on 
 their content

   publication.

3. Summary You can launch high speed WordPress website on AWS,

   just a few clicks; 
 If you choose AMIMOTO. Launching high speed WordPress website which doesn’t not make full use of AMIMOTO. True worth to utilise the AMIMOTO, which is “you can fully focus to your business”. We AMIMOTO development team has always carried out the service of design for it.

4. Technology base and services to support the Amimoto 1. Automation

   → Fully automation 2. Cloud Native → Full use of managed services 3. MicroServices → Implementing functions as loosely-coupled By taking advantage of the three points above, everyone can develop in easily the same quality of the environment and services, to enable the operational management. We are providing the platform to build environment "to focus on your business".

5. Issues to be solved 1.Dark side of WordPress: Hard to

   full use of AWS scaleabilities; 2.Bloated databases and tightly-coupled plugins: Hard to maintain WordPress;

6. The way to solve 1.The Infrastructure as Code with WordPress

   utilise JIN-KEI CloudFormation. 2.Modern developing approach with MicroServices and Server-less Architecture.

7. Session1

8. WordPress with Infrastructure as Code @Amimoto_Ami ja.amimoto-ami.com

9. Tentatively install plugins WordPress + Performance Manually server optimising Manually

   apps optimising

10. ʊਓਓਓਓਓਓਓਓਓਓʊ ʼSir? I can’t find AWS on itʻ ʉY^Y^Y^Y^Y^Y^Y^Y^Yʉ

11. Issues Google doesn’t scare me EC2 Dependancy More AWS you

    should learn By hand: the path to dark side

12. Automate them!

13. AutoScaling WordPress + Automation Utilise the Managed services Anyone can

    do it with CloudFormation

14. AutoScaling WordPress + Automation Utilise the Managed services Anyone can

    do it with CloudFormation

15. 8PSE1SFTT
    JT
    NBOBHFE
    TFSWJDFT
    GSJFOEMZ
    w "NB[PO
    3%4
    w "NB[PO
    4
    w "NB[PO
    $MPVE'SPOU
    w "NB[PO
    $FSUJpDBUJPO
    .BOBHFS
    w

    FUDʜ Managed Services 6TF
    .BOBHFE
    4FSWJDFT

16. 1IZTJDBM
    MBZFS 04 .JEEMFXBSF "QQMJDBUJPO 1IZTJDBM
    MBZFS 04 .JEEMFXBSF "QQMJDBUJPO Extent of

    Limitation of Liability Extent of Limitation of Liability EC2 Managed services

17. 3FEVDF
    UIF
    lTZTUFNT
    UIBU
    TIPVME
    CF
    NBJOUBJOFEz
    XJUI
    NBOBHFE
    TFSWJDFT Managed Services 6TF
    .BOBHFE
    4FSWJDFT

18. AutoScaling WordPress + Automation Utilise the Managed services Anyone can

    do it with CloudFormation

19. 8IFO
    UIF
    EFWFMPQNFOU
    NFUIPE
    BOE
    XPSL
    JT
    DPNQMJDBUFE
    BMM
    UIF
    EFWFMPQNFOUT
    XPVME
    EFQFOE
    PO
    UIF
    IVNBO
    QPXFS
    
    &WFO
    JG
    ZPV
    IBE
    MFWFSBHFE
    NBOBHFE
    TFSWJDFT

20. This architecture was ……

21. we have just built same system while ago. https://amimoto.doorkeeper.jp/events/41522

22. we have just built same system while ago. https://amimoto.doorkeeper.jp/events/41522

23. we have just built same system while ago. https://amimoto.doorkeeper.jp/events/41522 *G
    ZPV
    CVJME
    JU
    NBOVBMMZ

    
    
 JU`T
    BMMEBZXPSL
24. None

25. Automate linking up plugins CloudFormation Define resources by code Make

    unit with kumogata

26. Codes are opened to the public on GitHub https://github.com/megumiteam/amimoto-enterprise-cfn

27. Dividing the files to improve reusability _include 'include/vpc/vpc.rb' _include 'include/ec2/waithandle_ec2.rb'

    _include "include/security_group.rb" _include "include/elb.rb" _include 'include/iam/for_stack_001.rb' _include "include/cloudfront/cf.rb" _include "include/s3/s3-media.rb" https://github.com/megumiteam/amimoto-enterprise-cfn/blob/master/ include/001-base-resource.rb

28. Of course listed on AWS MP https://aws.amazon.com/marketplace/pp/B01B3ZE1NC/

29. Aurora edition is ready https://aws.amazon.com/marketplace/pp/B01B3ZE1NC/ "VSPSB
    3FBEZ

30. .BOVBMMZ
    
 CVJME
    TUBDL
    GSPN
    QJFDFT
    GPS
    BMM
    EBZ
 
 $MPVE'PSNBUJPO
    
 B
    GFX
    DMJDLT
    
    MBVODI
    JO
    NJO 8IJDI
    JT
    UIF
    CFUUFS
    TUB⒎
    GPS
    ZPVS
    CVTJOFTT

31. AutoScaling WordPress + Automation Utilise the Managed services Anyone can

    do it with CloudFormation

32. Bottle neck: file systems AutoScaling Automate scale up and down

    Auto recovery

33. 'JMF
    4ZTUFN

34. None

35. CloudFormation compatible http://docs.aws.amazon.com/ja_jp/AWSCloudFormation/latest/UserGuide/aws- resource-efs-filesystem.html

36. *U`T
    B
    QSFWJFX
    FEJUJPO
    OPX
    
 CVU
    JU`T
    NPSF
    UIBO
    UIBU

37. AutoScale architecture on 
 AMIMOTO Managed Hosting

38. 1FPQMF
    TBZ
 :PV
    TIPVME
    NBJOUBJO
    "VUP4DBMF
    BSDIJUFDUVSF UPP

39. GPS
    FYBNQMF
    w 8IBU
    XF
    BSF
    HPJOH
    UP
    EP
    JG
    $PEF%FQMPZ
    BHFOU
    IBT
    DSBTIFE
    w /PWJDF
    FOHJOFFS
    DBO
    CVJME
    TBNF
    TZTUFN
    TBNF
    BSDIJUFDUVSF
    w $BO
    XF
    TFMM
    UIFN
    PO
    "84
    .BSLFU1MBDF

40. Now Developing

41. Session2

42. AMIMOTO + Server-less Architecture @Amimoto_Ami amimoto-ami.com Server-less Architecture on AMIMOTO

43. Summary 1. Maintenance free infrastructure 2. Cost effective 3. Implementing

    functions as loosely-coupled with MicroServices On the feature developments of AMIMOTO, our developers commit to the implement the server-less architecture to reap the following benefits:

44. 1. Maintenance free infrastructure 2. Cost effective 3. Implementing functions

    as loosely-coupled with MicroServices

45. 1IZTJDBM
    MBZFS 04 .JEEMFXBSF "QQMJDBUJPO 1IZTJDBM
    MBZFS 04 .JEEMFXBSF "QQMJDBUJPO Extent of

    Limitation of Liability Extent of Limitation of Liability EC2 Managed services

46. 1. Maintenance free infrastructure 2. Cost effective 3. Implementing functions

    as loosely-coupled with MicroServices

47. Time Cost Time Cost EC2 Lambda

48. 1. Maintenance free infrastructure 2. Cost effective 3. Implementing functions

    as loosely-coupled with MicroServices

49. Current WordPress feature development 8PSE1SFTT
    $PSF
    1MVHJO
    1MVHJO
    

    1MVHJO
    1MVHJO
    1MVHJO

50. Issue that occur • Bloated source codes; • Bloated database;

    • Tightly-coupled features, core and themes ; • These will make Auto Scaling malfunction; 8PSE1SFTT
    $PSF
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO
    1MVHJO

51. Solution Idea: MicroServices

52. Microservices • Building system with multiple components; • Each component

    is able to run as an independents system; • Loose coupling; • Linking system with Restful API

53. 8PSE1SFTT
    $PSF $POOFDUPS
    1MVHJO "1* "1* "1*
    .JDSP4FSWJDF
    .JDSP4FSWJDF
    .JDSP4FSWJDF Future WordPress

    feature development

54. Implementation Case 1

55. Issue More power to search feature

56. 1. WordPress has simply LIKE search feature for title and

    body, have not full-text search feature. 2. Retrieval processing speed is rapidly decreasing if you customise the custom field in the search. 3. More contents published, more DB loads Issues

57. AMAZON 
 Elasticsearch Awesome Search

58. Architecture 8PSE1SFTT
    $PSF $POOFDUPS
    1MVHJO "1* ".";0/
    &MBTUJDTFBSDI

59. Implementation Case 2

60. Problem Visualise sales data through site search.

61. AMAZON 
 lambda AMAZON 
 DynamoDB AMAZON 
 API Gateway

    Implement visualising feature with Server-less Architecture

62. Architecture 8PSE1SFTT
    $PSF $POOFDUPS
    1MVHJO "1* "1* "1* 'VMM
    UFYU
    TFBSDI $PMMFDU
    TVCTDSJQUJPO
    EBUB 7JTVBMJTF
    

    TVCTDSJQUJPO
    EBUB
63. None

64. 'VMM
    5FYU
    4FBSDI %BUB
    7JTVBMJTJOH %BUB
    $PMMFDUJPO

65. None

66. Implementation Case 3

67. Problem Give us AMIMOTO user console page

68. Cognito 
 User Pools Awesome 
 user authentication infrastructure

69. None
70. None
71. None

72. Changes in development methodology with Server-less Architecture

73. Why development method is changed? 1.Develop, test and deploy them

    in the world without SSH; 2.Rendering transition: server-side to client-side; Wu will not be able to use the development method which has been developed on the assumption that the server is present.

74. 1. Develop, test and deploy them in the world without

    SSH; 2. Rendering transition: server-side to client-side;

75. • Project management with API Gateway and Lambda; • Run

    Lambda in locally; • Centralised configuration of API Gateway; • Switching development, staging and production stage; • Deploying to AWS; • Publishing your homebrew apps to GitHub; Serverless Framework

76. 1. Develop, test and deploy them in the world without

    SSH; 2. Rendering transition: server-side to client-side;

77. • Rich UI library specialised in View; • Rendering with

    precompiled; • Lightweight, easy to coding; • Easy to make the application for the API Gateway Lambda as a View; Riot.js

78. http://qiita.com/horike37 For more detail about the architecture, I've already posted

    to Qiita, includes source code. Check out my Qiita page. Thanks!

79. Conclusion

80. Issues and Solutions 1.Dark side of WordPress: Hard to full

    use of AWS scaleabilities; 2.Bloated databases and tightly-coupled plugins: Hard to maintain WordPress;

81. We’ll resolve them all

82. Issues and Solutions OK, now we can develop it with

    automation. 
 What about the operations?

83. ʊਓਓਓਓਓਓਓਓਓਓਓʊ ʼMake operation automateʻ ʉY^Y^Y^Y^Y^Y^Y^Y^Y^Yʉ

84. Next Stage

85. @Amimoto_Ami amimoto-ami.com THANK YOU!