Source Allies Logo

Blog Insights

  • Example of mixed UI components

    Micro-Frontend Strategy

    Leveraging multiple front-end code bases can be achieved without sacrificing flexability and team atonomy.
  • Making a Market

    Material Market: Coordinating Distributed Events

    A simple way to coordinate events without locking on AWS.
  • Centralized Data

    Reference Data Without the Database

    Not all micro-services need to be built the same way. In this post we walk through an alternative way of designing APIs for slowly changing reference Data.
  • An image of a rollercoaster, representing the management of technology lifecycle

    Technology Lifecycle Management

    The future of tech stack efficiency is here. For companies to mature in their IT Strategic financial forecasting, Technology Lifecycle Management will need to be a focus area
  • cloud image to represent infrastructure as code and cloud development best practices

    Case Study: Leveraging Infrastructure as Code and DevOps Best Practices

    Source Allies saw an opportunity for our partner, a Fortune 500 agriscience company, to accelerate their digital transformation. In its current state, there were a dozen software development teams working on the same product who did not have confidence in the stability of their current cloud infrastructure and deployment environments....
  • Developer coding at a workstation

    Deploying AWS APIs with the Serverless Framework

    ...
  • two teammates pairing at a work station looking at code

    Case Study: e-Delivery Platform Development and Adoption

    We believe companies that invest in great technology products can achieve strategic competitive advantages within their market, regardless of industry or size. This can be especially true during COVID times, when companies are looking for ways to make it easier to connect with their customers. Accessibility and product ease can be one of the...
  • Colored pipes in an industrial setting

    Event Sourcing

    Software development teams are responsible for building a wide variety of software to solve a wide variety of problems. Many of these software development projects implement business flows that have defined activities completed by specific parties. An architecture that implements these flows by mixing validation logic with record updates becomes...
  • Teammates sitting together and looking at code

    Node Reference - Conclusion

    Prerequisites This article builds on the prior article: The "Join" Problem. Conclusion In this series, we walked the reader through the considerations of building a production-ready microservice. More important than the tools we used (e.x. NodeJS, AWS) were the questions we asked. You may choose different tools and libraries for your applications, but it is...
  • Teammates sitting together and looking at code

    Node Reference - Change Events

    The "Join" Problem Modern applications no longer exist in a silo. They need to integrate with other systems within the organization. In a microservice architecture, this is even more valid since very few business processes can be completed by involving only one service. Let us suppose that our product service is the new source...