BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Architecture Content on InfoQ

  • Microservices, DevOps and PaaS - The Impact on Modern Java EE Architecture

    InfoQ sat down with Markus Eisele, developer advocate at Red Hat, at the Devoxx BE conference, and asked about his thoughts on implementing microservice architectures within large-scale enterprise organisations. The conversation was primarily based on his recent O'Reilly mini-book publication, “Modern Java EE Design Patterns: Building Scalable Architecture for Sustainable Enterprise Development".

  • Redux: An Architectural Style Inspired by Flux

    Redux uses a unidirectional data flow similar to Flux, but it has a single store which is changed by cloning the original store and applying some functions without side effects. There is no Dispatcher.

  • The AWS Well-Architected Framework

    Amazon has published the AWS Well-Architected Framework, a guide for architecting solutions for AWS, with design principles that apply to systems running on AWS or other clouds.

  • Big Data Architecture: Push, Pull, or Search in Place?

    A surprisingly common theme at the Splunk Conference is the architectural question, “Should I push, pull, or search in place?”

  • Key Takeaways from the 'Agile on the Beach' Conference: Day One

    At the fifth ‘Agile on the Beach’ conference, held in Cornwall, UK, several leading practitioners of agile software delivery presented the state-of-the-art and emerging trends within this domain. Key messages included the need for the more rigorous use of the scientific method throughout the software delivery lifecycle, and the benefits provided by applying agile principles to product development.

  • Building Microservices with Go and ‘Go kit’: Peter Bourgon Q&A

    At the Golang UK Conference, Peter Bourgon introduced ‘Go kit’, an open source microservice toolkit that can be used to facilitate and standardise the creation of Go-based services within the modern enterprise application stack.

  • 10 Properties Defining Software Architecture

    Software architecture is a process; a sequence of strategic design decisions mapping specification and business goals to architecture design, and a thing; a set of views produced by the process that address different stakeholders, Michael Stal states describing how to define a software architecture.

  • Introducing DDD in a Project at “Which?”

    After failing with two proof of concept, mainly with scalability issues, when trying to renew their main website the business decided to take a more agile and incremental approach and in a restart of the project inspired by Domain-Driven Design (DDD) having developers talk with domain experts, Chris Patuzzo explains describing the principles of DDD in the context of a real project.

  • Moving Towards Integral Quality

    Olaf Lewitz gave a keynote about Integral Quality at the Agile Testing Day Netherlands 2015. InfoQ asked Lewitz about quality attributes, what causes poor quality software, the relationship between the structure and culture of the organization and software quality and about clarifying intent and increasing trust.

  • A Critical Look at CQRS

    Looking at Command Query Responsibility Segregation (CQRS) in a larger architectural context there are other architectural styles available. There are database technologies solving the same problems but in a simpler way, Udi Dahan states looking into ways of approaching CQRS. There is also a way that fulfils a lot of the CQRS goals but with fewer moving parts when CQRS is really needed.

  • Software – Is it "Engineering" Yet?

    At the GOTO Amsterdam 2015 conference Mary Shaw talked about progress towards an engineering discipline of software. She explored what it means to have an engineering discipline, how far we have progressed toward having one for software, and what can be the next steps.

  • Why Scrum is Not Enough

    When developing large complex systems and dealing with legacy code, organizations need to have systems in place to support integration and delivery. Modularization can help when agile is scaled with multiple teams that are working in parallel. It's not the framework or method that will do the job, but how your people will make it work to solve your problems says Hans Dekkers.

  • Scaling the Stack Overflow Monolithic App by Obsessing Over Performance

    At QCon New York 2015, David Fullerton presented a deep-dive into the monolithic C# / MS SQL architecture that powers the Stack Overflow website, which handles over 4 billion requests per month. Fullerton argued that by focusing on performance, scalability was included ‘almost for free’; and that by minimising the number of external application services, the need to pay ‘SOA tax’ has been avoided.

  • How NGINX Achieves Performance and Scalability

    Owen Garrett, heads of products at Nginx, Inc., has described on Nginx’s blog which design decisions allow NGINX to provide top-in-class performance and scalability.

  • Stefan Tilkov: Skip the Monolith, Start with Microservices

    During the last months Martin Fowler among others have claimed that a microservices architecture should always start with a monolith, but Stefan Tilkov is convinced this is wrong, building a well-structured monolith with cleanly separated modules that later may be pulled apart into microservices is extremely hard, if not impossible in most cases.

BT