BMC AMI DevX is an integrated software platform that provides mainframe development teams with modern Application Development and DevOps capabilities. The solution connects traditional mainframe environments with contemporary development practices through components for source code management, testing, debugging, and analytics.
N/A
Pantheon
Score 9.8 out of 10
N/A
Pantheon is a WebOps platform where marketers and developers collaborate to drive results. The vendor states that with Pantheon, site owners maximize their capacity to update website design and functionality, responding to market trends, catering to consumer behavior, and adding real value to the business's bottom line. Today, companies compete on the basis of digital experiences, and the best results emerge from an agile build-test-learn process. Whether it's publishing content,…
$29
per month
Upsun
Score 9.9 out of 10
N/A
Platform.sh helps companies of all sizes, from SaaS entrepreneurs looking to build, run, and scale their websites and web applications.
Acquia was terrible. We use DigitalOcean for some all-purpose computing needs and Platform.sh for an application that does more computing and high-throughput processing where we do not want page views (API calls) to count against our usage.
We use several hosting solutions depending on the client needs or what they were already setup on. Pantheon is very similar to them and offers similar services however one of the main features we use is the Multidev service which allows us to test pieces of work separately and …
In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. …
I love these tools! However, my company has not yet transitioned from SCLM to a modern repository, and this is causing most of our developers to remain within TSO for all their development. It's been a slow adoption up to this point, but we are moving toward more modernization this year and next, so with any luck, we'll see usage pick up. Success depends on the speed at which your management is willing to move.
Pantheon is excellent for medium-large websites that require high availability and a managed workflow. It would be inappropriate for small websites because of the cost or for situations where more control of the environment is appropriate. We find it useful because we rarely do anything outside of the Drupal application.
In our organisation we are the only team that uses Platform.sh to host any site. This was a cost effective way for us as we were using Acquia Cloud earlier for these websites. We mostly use Platform.sh for those sites which are always in development as it is simpler and faster to handle these operations in Platform.sh. Then we do a lift and shift to Acquia as we move more towards the go live and post production maintenance side.
The tool I use is fairly intuitive. It doesn't take long to be using it full time.
Changing the layout/view is fairly easy. This allows it to fit individual preferences.
It is helpful to be able to view specific windows in full screen. Usually, I have it set up to view multiple windows, but sometimes, I just want to view one window in full-screen mode.
the debug utility is very useful. Place stopping points is easy and one can set parameters as to when you stop at a line of code. Changing the data on the fly is easy and usefull. The interface is easy to use and make sense.
Platform.sh is not for beginners in my opinion. It has a good amount of learning curve in my opinion.
As this is a PaaS, teams habituated with cloud infrastructure may miss the server side support from their cloud teams. I believe you will have to work on server bugs more on your own.
During normal maintenance periods, integrations may fail if you are working on your sites in that time, in my experience.
Pantheon is an easy system, especially to the users with previous experience with other similar platform and the interface is clear enough to easily understand how things operates. On the Cloud deployment everything also works effectively and the technical team from Pantheon community are very helpful on providing the necessary assistant to their customers.
Support has been amazing compared to Optim. Further, new features are very regular with File-AID - I can't remember the last time Optim had a significant update. File-AID support is very receptive to feature requests and reported bugs, including sending out hotfixes quickly.
Even tier 1 Pantheon chat and ticket support are knowledgeable, competent, and useful. They routinely understand and promptly resolve urgent, complex, and/or unusual issues that other hosts need to escalate to tier 2 or tier 3 support personnel. I honestly can't think of a truly negative or disappointing support experience in the years I've used Pantheon hosting for client websites.
The installation teams for these products have never complained about any difficulties during the integration of this range of tools into our IT system.
The names may have changed over the years, but anyone who has been around for a while will recognize them. For Software Configuration Management, I have used TSO/ISPF/SCLM, Panvalet, ChangeMan, Librarian, Endevor, and now Code Pipeline. All of them met the basic requirements. All of them had their advantages and disadvantages. Code Pipeline, however, stands head and shoulders above the rest in simplicity, completeness, effectiveness, efficiency, and elegance.
Although it may seem a good fit for a company that needs extra control over the deployment process and development process, for a firm that is mainly concentrating on SEO, it would be an overkill. Pantheon provides that sweet automation that allows us to shed some weight on development and focus on our business activities.
In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. After said development is done, we generally lift and shift to Acquia for more content heavy sites and to AWS for more transaction oriented sites.
Possitive impact. It is main product suite to enable devops in the mainframe applications team. All developers use these on day-to-day work.
Negative impact: Recent usability issues caused disappointment in the application teams. It became hard motivate the development community to increase usage.