Modern serverless applications on AWS are complex with a lot of moving parts. Mapping a developer workflow onto those applications can be difficult. This article discusses the developer workflow I have developed for complex serverless applications at aleph0, with example CloudFormation template and GitHub Action snippetes to illustrate the concepts. Goals for Developer Workflow An
I show how traditional web-server applications compare with their serverless counterparts. I show how the infrastructure is managed for you in serverless, and how code for serverless developers in primarily focused on business logic.
Software engineers have been ardently following Test Driven Development (TDD) as an XP practice for having necessary safety nets. I have even tried covering …
How to build distributed systems with Ruby on Rails
Building an application with a microservice architecture is a long-term decision if you can afford the increase in upfront time investment to do it properly. Heroku provides a platform that simplifies microservices architecture.
Barry Jones - Fractional CTO. Your team is talented and capable, so why are they always overwhelmed?
Schema-ify the Web
Service Design, Enterprise Design, UI, UX, HTML, CSS and IndieWeb
I believe we should look beyond libraries and frameworks and rediscover the value of patterns and principles, and I’d argue that it would lead us to have less breaking changes and add more longevity to the stuff we build.
Service Design, Enterprise Design, UI, UX, HTML, CSS and IndieWeb
Although incredibly effective, DDD is overlooked by developers because of its abstractness. Here is a set of hacks to introduce DDD during an Event Storming workshop. Ex: Alternatives to convoluted DDD names, Group activities to pass a concept through, Presentation material for tricky notions
What a good design artifact looks like, what they’re actually for, and how to use them efficiently to achieve a better outcome for your project.
I’ve been building enterprise Java web apps since servlets were created. In that time the Java ecosystem has changed a lot but sadly many enterprise Java developers are stuck in some very painful and inefficient ways of doing things. In my travels I continue to see Java The Sucky Parts - but it doesn’t have to be that way. It is time for enterprises to move past the sucky ways they are using the Java platform. Here is a list of the suckiest parts of Java that I see most often and some recommendations for how to move past them.
Build an admin app to keep logic seperate in Meteor.js
Okay, campers, rise and shine...
This is a follow-on to my earlier post on automatic application modernisation . In application modernisation the goal is to reduce a larg...
A clear presentation of the kind of tools you need to develop your software project, including their usage.
Swift recently achieved ABI stability, meaning that we can now ship Swift binaries without having to ship the corresponding Swift libraries....
🧘♀️ Lightweight fault tolerant primitives for your modern asyncio Python microservices - roma-glushko/hyx
Schema-ify the Web
The year is 2022, and Kubernetes is wreaking havoc on software delivery as we know it. Applications are going through modernization programs so they can be converted into microservices, but they are coming out the other end as distributed monoliths. Next thing you know, services exist across several clouds and even in your data centers. And, of course, the large majority of enterprises aren’t just greenfield.
Overview
WASM: universal application runtime Last summer, fresh off my last freelance gig, I was catching up with my friend Asim, the founder of the widely popular microservices company, Micro at one of our favourite coffee shops in London. We would end up meeting almost every week talking about the presence and the future of technology. But that day our conversation turned into something that we had not talked about for a long time: Web assembly (WASM).
This is part 2 of the Revisiting Augmenting Human Intellect series, where I break down Douglas Engelbart's Augmenting Human Intellect, the classic paper on how…
Sharing my retrospective on building a complex web application as an Engineering Manager
From their first introduction in 2005, the debate between adopting a microservices architecture, a monolithic service architecture, or a hybrid between the two has become one of the least-reversible decisions that most engineering organizations make. Even migrating to a different database technology is generally a less expensive change than moving from monolith to microservices or from microservices to monolith. The industry has in many ways gone full circle on that debate, from most hyperscalers in the 2010s partaking in a multi-year monolith to microservices migration, to Kelsey Hightower’s iconic tweet on the perils of distributed monoliths:
To PAAS or not to PAAS | The ramblings and ranting of Ivar Abrahamsen at flurdy.com.
How to create an Augmented Reality app that allows a user to get content recommendations.
Ten years ago today I announced the launch of Amazon S3 with a simple blog post! It is hard to believe that a decade has passed since then, or that I have written well over 2000 posts during that time. Future Shock When I was in high school, I read and reported on a relatively […]
Daily technology videos, curated by Reuven Lerner.
Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards. - donnemartin/system-design-primer
Terrain vague in a city is abandoned space without clear purpose. Does it also exist in programs and can we learn something useful about reading programs and the space in which program exist from the inter-disciplinary study of terrain vague in cities?
Introduction 该篇文章主要要用说明为什么要写这一系列的原因。在该系列中会按照搭建微服务的各个阶段所依赖的各个组件一个一个的去探索和分析碰到了什么问题，如何解决问题。 Series API Gateway CI & CD Service Discovery Communication between Services Configuration Center Monitoring & Observability Transaction & Distributed Lock Manager Tips 本人报以60分的心态启动的该系列写作，理解有偏差或错误的请帮忙指出。后续会根据自己的认知的提升而进行改进文章。 What 什么是Microservices? Microservices是一种开发软件的架构和组织方法。通过把软件划分成多个独立的服务，服务之间通过明确的API来通信，每个服务拥有独立部署和迭代的能力。 From Monolithic to Microservices 商业公司刚起步时，为了能快速迭代和上线功能，通常会采用单体应用（Monolithic）即应用的所有功能都在一个服务中进行开发和迭代。当公司的业务越来越多，单体应用的功能也会越来越多，开发人员也会越来越多，此时某个功能出现问题将影响到整体的可用性（单体应用随功能越来越多还会有其他的问题，此处只举一个关键的例子），而通常公司会采用微服务（microservices）的架构，把单体服务拆分成多个独立服务，服务间通过明确的API来通信，从而避免由于单点故障导致全局崩盘。尽管使用微服务架构可以避免该问题，但通过也带来了不少的“麻烦”，不同功能之间调用，原本只需要本地调用，现在需要依赖跨进程/跨机器调用（RPC/HTTP）并且需要考虑到调用失败的重试/容错处理；服务增多为了提升部署的效率和可靠性需要构建高效的CICD系统等等。权衡下来对于业务较复杂的大型商业公司来说，微服务是一种适用的解决方案。 Why 写该系列的原因 以练促学：工作中较少有机会能完整的搭建微服务，通过实践提升对微服务的认知 How 业务场景 UGC音乐平台（MusicHub）- 用户在该平台上即使创造者也是消费者，用户可以自由创作音乐，消费音乐。 仓库地址：https://github.com/yuhangbin/music-hub 歌曲服务(Song Service) 发布歌曲 获取歌曲信息（包含创作者信息） 歌单服务(PlayList Service) 用户可以通过歌单功能，实现自定义歌单 创建歌单 更新歌单 获取歌单（包含歌曲信息） 用户服务(User Service) 查询用户信息 注册 更新个人用户信息 系统设计 References Microservices Patterns With examples in Java (Chris Richardson) https://icyfenix.cn/ https://en.wikipedia.org/wiki/Microservices https://aws.amazon.com/cn/microservices/ https://microservices.io/ https://en.
Evil staging and gauntlet programs are chaos engineering inspired, systemic approaches to improve software reliability.
Is your Web application is getting a bit big and bulky on a single server? You might be thinking of moving to a more distributed, microservice-based architecture. And in many cases, that’s a great way to go about things. But microservices aren’t a panacea, having their own issues and pain points. What are the trade-offs … Continue reading [Video 454] Ben Christensen: Don’t Build a Distributed Monolith →
This is a blog post that I originally wrote for the edX engineering blog. At the core of edX is the edx-platform, a monolithic Django code-base 2.7 times the size of Django itself.
Erbosoft Metaverse Design Solutions