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

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

Bdaf0b291f02fe64a02cdf592a8a0c8f?s=128

AMIMOTO

May 18, 2016
Tweet

Transcript

  1. 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. 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.
  3. 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".
  4. 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;
  5. 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.
  6. 11.

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

    should learn By hand: the path to dark side
  7. 16.

    1IZTJDBMMBZFS 04 .JEEMFXBSF "QQMJDBUJPO 1IZTJDBMMBZFS 04 .JEEMFXBSF "QQMJDBUJPO Extent of

    Limitation of Liability Extent of Limitation of Liability EC2 Managed services
  8. 24.
  9. 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
  10. 34.
  11. 41.
  12. 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:
  13. 45.

    1IZTJDBMMBZFS 04 .JEEMFXBSF "QQMJDBUJPO 1IZTJDBMMBZFS 04 .JEEMFXBSF "QQMJDBUJPO Extent of

    Limitation of Liability Extent of Limitation of Liability EC2 Managed services
  14. 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
  15. 52.

    Microservices • Building system with multiple components; • Each component

    is able to run as an independents system; • Loose coupling; • Linking system with Restful API
  16. 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
  17. 61.

    AMAZON 
 lambda AMAZON 
 DynamoDB AMAZON 
 API Gateway

    Implement visualising feature with Server-less Architecture
  18. 63.
  19. 65.
  20. 69.
  21. 70.
  22. 71.
  23. 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.
  24. 74.

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

    SSH; 2. Rendering transition: server-side to client-side;
  25. 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
  26. 76.

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

    SSH; 2. Rendering transition: server-side to client-side;
  27. 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
  28. 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!
  29. 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;
  30. 82.

    Issues and Solutions OK, now we can develop it with

    automation. 
 What about the operations?