Skip to content

Write the History of SeedStack #60

Open

Description

@cmmatei

Describe in a few words the evolution of SeedStack

Activity

  1. self-assigned this
    on Mar 23, 2016
  2. cmmatei commented on Mar 24, 2016

    @cmmatei
    MemberAuthor

    Since years industrialize the applications development was the mainstream. The deciders in big organizations wanted to realize projects easily, less costly, in a short time to market, have a good quality, be compatible with the legacy and also to be modern. A lot of objectives, some of them being contradictory at a first glance.

    Add to these goals the need to govern the architecture of the projects and the canvas is ready.

    In 2012 we were an experienced team in developing java/web applications and assembling basic frameworks. We were convinced that the rise of new techniques or paradigms like Rest, JavaScript frameworks and Single Page Applications, Domain Driven Design or patterns as CoC would change the developer experience and accelerate the modularity of the projects.

    In 2013, we had the opportunity to be entrusted with the definition of a new enterprise software stack. We found the common denominator of these requirements: our ambition as craftsmen to design, code, practice and draw the governance of the best application development stack.

    After six month we released the first version of SeedStack on the 15th of October 2013. Since then over than 50 applications have been developed by more than 300 craftsmen.
    We had the chance to be supported by the whole IT staff and report them our advancement every month. Developers from worldwide and suppliers came with us to embrace our concepts and make their applications modern and attractive.

    A release plan was established annually to give more perspective to the users of how the project evolves.

    After 2 years of usage of SeedStack by our clients, we were more convinced than ever that what lasts in software, is the business you model and code inside applications. Two key factors that make you successful for the final user: UX experience and the functional features you provide. But concerning the coders what make you successful is the fact that the framework is designed for them and they find their own ideas inside.

    SeedStack was considered being a real success and the IT staff was proud to open source SeedStack in April 2015.

  3. cmmatei commented on Mar 24, 2016

    @cmmatei
    MemberAuthor

    First version of the timeline.

  4. cmmatei commented on Mar 25, 2016

    @cmmatei
    MemberAuthor

    Since years industrialize the applications development was the mainstream. The deciders in big organizations wanted to realize projects easily, less costly, in a short time to market, have a good quality, be compatible with the legacy and also to be modern. A lot of objectives, some of them being contradictory at a first glance.

    Add to these goals the need to govern the architecture of the projects and the enterprise application development canvas is ready.

    In 2012 we were an experienced team in developing java/web applications and assembling basic frameworks. We were convinced that the rise of new techniques or paradigms like Rest, JavaScript frameworks and Single Page Applications, Domain Driven Design or patterns as CoC would change the developer experience and accelerate the modularity of the projects.

    At that time, we've been entrusted with the definition of a new enterprise software stack. We found the common denominator of these requirements: our ambition as craftsmen to design, code, put in practice the best application development stack and draw the governance of the software developed within.

    After six months we released the first version of SeedStack on the 15th of October 2013.

    Since then over than 50 applications have been developed by more than 300 craftsmen.
    We had the chance to be supported by the the projects and be under the governance of the IT staff. We reported them our advancement in an agile manner. Developers from worldwide and suppliers came with us to embrace our concepts and make their applications modern and attractives.

    A release plan was established to give more perspective to the users of how the project evolves.

    Since its first enterprise version, 13.11, SeedStack evolved to a customizable and extensible solution at multiple levels. Beyond configuring and extending each component, developers can tailor the whole stack to the organization needs.

    A strong concept of framing business development emerged in SeedStack from the Domain Driven Design approach. It represents the answer to improve quality code and give a real value to the applications by capitalizing on their business code. A Business Framework implements the DDD aspects in order to provide to the enterprise development teams tools to better design, reuse, and ease the maintenance of the functional code. SeedStack provides thus the tools to frame and drive enterprise application development projects and helps development experts to focus on the design and development of the business code.

    Nowadays SeedStack covers the essential needed to design and implement modern applications with respect to cloud environment or monitoring issues.

    After more than 2 years of usage of SeedStack by our clients, we were more convinced than ever that what lasts in software, is the business you model and code inside applications. Two key factors that make you successful for the final user: UX experience and the functional features you provide. Concerning the coders what make you successful is the fact that the framework is designed for them and they find inside their own ideas.

    SeedStack was considered being a real success and was put on open source SeedStack in April 2015.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions