Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Jimi Wikman
    Jimi Wikman

    Atlassian introduces their new cloud development platform Forge

    • Interresting 1

    Earlier in 2019 Atlassian presented their new cloud development platform FORGE at the Atlassian Summit. The idea is to have a tool that makes it easier and faster to develop apps for the Atlassian cloud suite using a serverless FaaS hosting platform, powered by AWS Lambda.

    This new cloud development platform will probably be a welcome tool for new app developers and if received well it will push development for cloud to the front lines. All in accordance with the business strategies Atlassian seem to push towards cloud in general.

    According to the article by Atlassian, Forge comes with three core components:

    1. A serverless Functions-as-a-Service (FaaS) hosted platform with Atlassian-operated compute and storage for app developers
    2. A flexible declarative UI language (Forge UI) that enables developers to build interactive user experiences across web and devices with just a few lines of code
    3. A state-of-the-art DevOps toolchain, powered by the intuitive Forge Command Line Interface (CLI).


    A serverless Functions-as-a-Service

    The first component with the FaaS I think sounds excellent as one of the big hurdles with app development for Atlassian (and other systems) is hosting and develop the app as a separate web service. Having FORGE do the heavy lifting should make that threshold a bit lower (depending on the cost of course).


    Forge solves very real problems for developers by removing some of the complexity (and cost!) associated with cloud app development. Creating apps for most cloud ecosystem platforms holds developers responsible for building, hosting, and operating an entirely independent web service, which requires expertise in cloud architecture and management.


    Atlassian list 3 specific areas that they hope that FORGE will help with:

    1. Trust: As personal information goes digital, privacy, transparency, and security are more important than ever before. With Forge UI, developers and app consumers benefit from built-in, best-in-class security for apps, by default. Plus, thanks to Atlaskit, when Atlassian makes an update, your apps won’t break.
    2. Running anywhere: Atlassian customers want experiences that are consistent across their products and apps, and across their devices and web. Forge’s UI enables users to build once for both web and mobile.
    3. Moving up the stack: In general, developers aren’t concerned with where their code is running – they simply want to spend less time on implementation details of the code, and more time on providing customer value. Forge’s serverless FaaS model enables developers to write single functions rather than building entire web applications.


    There are also other areas where FORGE can help reduce pain points and increase security.


    A FaaS platform also lets developers eliminate common pain points such as authentication, identity, scaling, and tenancy. Apps created with Forge will run inside a second security layer that enforces tenancy isolation and data egress restriction by design, which translates into more meaningful security and privacy guarantees for Atlassian users.


    A flexible declarative UI language

    The second part I am not sure if it's a good thing or not. For anyone developing only towards cloud based Atlassian systems it is of course awesome as it makes things easier and we get a more unified design across apps as well as systems. It is when dealing with multiple ecosystems such as Server or Data Center this can become a bit complicated.

    On one hand it forces even server based apps to follow the design specifications of Forge UI, but on the other hand it can limit the app developers. Overall it should still be a good thing and as it is based on Atlaskit it should be pretty well aligned with the overall UI design for cloud.


    Using Forge UI – one of the core components of the new platform – developers can create and customize apps in minutes. It’s a declarative language, making it easy to quickly build native, flexible, and trusted UI interfaces for apps. By building on the Atlassian infrastructure, an app’s user experience becomes more consistent with our product’s user experience by consistently running the latest version of Atlaskit – a win for developers and our customers.


    A state-of-the-art DevOps toolchain

    For the DevOps toolchain I would like to know more before making any assumptions as it seem to be based on Bitbucket pipelines that are still quite new.  I like Bitbucket Pipelines, but I would like to see if this is just a built in version of it into FORGE or if it has some changes.

    Things like defining environments within AWS Lambda and what the UI for this will look like. Is it "just" a CLI and if so, what capabilities can I expect within the CLI itself. Will this be connected to Bamboo for the build or can I choose other build tools such as TeamCity for example?

    The fact that this part is barely mentioned in the article of the presentation is a bit of warning flag for me. If it is state-of-the-art, then please show me the tool chain and give me an example of a simple code update from development to production. Still, this is just me being a bit nit-picky as I am sure there are already videos out there for this or they will come soon enough.

    Overall I think this will be a bit of change for many app developers today, but a good change.


    The Forge CLI – another core component of the new platform – is a command line interface tool that makes managing Forge apps easy. We’re creating resources like built-in onboarding, intuitive commands, and a set of templates that anyone can use, making the process of getting started with Forge easy. In addition, the creation, testing, and deployment of apps is part of a DevOps toolchain with continuous delivery powered by Bitbucket Pipelines.


    Welcome to the Forge - Presentation at Atlassian Summit 2019


    Personally I think this is a great thing that will help app developers a lot. Old app developers might need a while to adjust, but in the long run I think it is a good thing. Adding this service not only ensure that things get more uniform in terms of design and coding, but it also will provide great insight into how a controlled DevOps toolchain is perceived outside of their own company.

    I look forward to learn more about Atlassian Forge that is currently in Closed Beta that you can sign up for here.


    What do you think of Atlassian Forge so far?



    Edited by Jimi Wikman

    User Feedback

    Recommended Comments

    There are no comments to display.

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By ©Jimi Wikman
      The requests to get Portfolio for Jira for Cloud users have been loud and finally Atlassian released a Cloud version. They also made a very odd choice to rename Portfolio for Jira to Advanced Roadmaps and place it behind the Cloud Premium barrier.
      Portfolio for Jira has long been the better choice for Jira Server and Jira DC users. The features have been perfectly suited for managers to keep an overview over large programs and initiatives with relative ease. As such it has been the envy of Cloud users for years and it comes as no surprise that Atlassian would port this to Cloud given their focus on the cloud platform lately.
      Renaming Portfolio for Jira is also no surprise as it confuse managers with two portfolio products where the high level Portfolio tool Jira Align is the product Atlassian seem to want to focus on. Renaming it to Advanced Roadmaps is however a very strange choice as it is not a simple roadmap tool. It also make the naming confusion shift from Portfolio to Roadmaps as Cloud users have been using the limited Roadmaps feature for quite some time.
      The new Advanced Roadmaps is only available for Cloud Premium users. This makes sense as Atlassian want to push users into their new price model. Currently there is not much that would warrant double the price for Cloud Premium so Atlassian need something that is enticing enough for users to make the shift. Advanced Roadmaps could be one of those features, but they need more as Advanced Roadmaps cost $2.3/user and month at it's lowest level and Cloud Premium cost an additional $7/user and month.
      Feature wise Advanced Roadmaps is still great with the two main selling points of great overview and the ability to scale the issues with more levels. Here are some of the selling points from Atlassian:
      With the changes coming to Roadmaps where all projects will get them, and not just Next-Gen projects, combined with the promise that Advanced Roadmaps will somehow be connected to a more comprehensive whole this could be a pretty good thing for Cloud Premium users. Adding Advanced Roadmaps to Cloud Premium will now add the ability to scale issue types beyond the standard 3 levels, which is something people have asked for for a very long time.

      Will it be enough to warrant the high price tag for Cloud Premium? I doubt that as Advanced Roadmaps is only really useful when you pass a certain number of teams. Doubling the price tag will probably discourage most low to mid-range clients. The fact that you can only have a 7 day test version and that you need to setup a new cloud instance to even test this if you are on a regular cloud plan is also a problem. With more features added into Cloud Premium however I think more and more will make the shift over to that.
      Overall this is a good new addition and package it with the Cloud Premium offer will make it more accessible and therefore used, which is a good thing. It's a bit sad to see Atlassian being so aggressive in their way of forcing cloud users into their Premium tier that is making some old customers a bit annoyed, but I think it will be good in the long run.
    • By ©Jimi Wikman
      This video is about Halp's integration with Microsoft Teams. If you'd like more information or to try Halp in Microsoft Teams visit https://halp.com/microsoft-teams
    • By ©Jimi Wikman
      Atlassian has announced that they have acquired Halp. Halp is an interesting take on support for Slack that allow you to create support tickets directly from conversations in Slack. As Halp can also be integrated with Jira Service Desk it makes sense for Atlassian to make the investment to purchase Halp to further strengthen their service portfolio on the support side.
      Halp have made a bit of an impact in its only 12 months life span and with the simplicity of just posting an emote in Slack to create separate support tickets it has been a hit. Good integrations with Jira Service Desk and Zendesk has of course been a big part and now with integrations to Microsoft Teams it is even better.
      Not only will Halp make it so much easier to keep track of support questions in Slack, but by integrating with other tools such as Jira Service Desk, then you have a powerhouse. It will update on both sides of the integration allowing you to meet your clients where they feel most comfortable and still maintain proper workflows. You can even connect it to Confluence or Slack messages to create knowledge bases.
      This is of course another step to connect closer to Slack that purchased the rights to Atlassians previous chat products. Naturally Slack is very happy about this acquisition:
      In the future we will see deeper integrations with Jira Service Desk and Confluence for sure, but there are hints forr new integrations with OpsGenie and Trello for example. It will undoubtedly be an interesting journey to follow in the future.
    • By ©Jimi Wikman
      Dedicated to developers, business analysts, testers, and test managers, Requirements and Test Management for Jira combines all aspects of software development, including requirements, tests, and bug reporting, into one intuitive tool.
    • By ©Jimi Wikman
      Halp is the first conversational ticketing solution for operational support teams to assign, prioritize, and answer requests from Slack in a message-based interface. Companies using Halp get faster response times, more productive Ops teams, and happier employees.
  • Create New...