Plugin Developer • Serverlessconf Tokyo 2016,2017,2018 speaker • Remote worker (in Sapporo-shi, Hokkaido) • The best Serverless Architect in Japan !!(Ͱ͋Γ͍ͨʣ MASASHI TERUI ARCHITECT / DEVELOPER
and security was managed by the central server application. In the Serverless version there is no central arbiter of these concerns. Instead we see a preference for choreography over orchestration, with each component playing a more architecturally aware role—an idea also common in a microservices approach.” https://martinfowler.com/articles/serverless.html
a series of steps in a business process” • “Strongly promotes the microservices model, as most serverless runtimes enforce limits on the size or execution time of each individual function” • “Is the latency between the microservices, vs co-located features within a single deployment, an issue?” • “Once an application is split into multiple components, or microservices, you then have the freedom to deploy each one separately on completely different infrastructures, if that’s what’s best for your needs.” • “Likewise, each microservice can also be developed with the best technology (i.e. language) for its particular purpose. The freedom that comes with "breaking up of the monolith" brings new challenges though, and the following sections highlight some of the aspects that should be considered when choosing a platform and developing your microservices.” CNCF SERVERLESS WHITEPAPER
one table, unless there is a specific reason for using multiple tables” • “Schema-less” ͷҙຯΛߟ͑Δ • List, Map͕࣋ͯΔ͜ͱʁ • શͯͷAttribute͕ඞਢͰͳ͍͜ͱʁ • A. ͳΜͰಥͬࠐΊΔ͜ͱ • దʹࢄͤ͞ΒΕΕςʔϒϧΛ͚Δඞཁ͕ͳ͍ https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-general-nosql-design.html DynamoDB Best Practices