62 results found

    Blog Posts (41)
    • Cedrus Achieves AWS Well-Architected Partner Status

      [January 12, 2021]– Cedrus, a highly sought-after digital transformation solutions provider and AWS Consulting Partner, announced today that it has achieved the AWS Well-Architected Partner status, which recognizes that Cedrus has the expertise to deliver AWS Well-Architected reviews for existing application workloads or new applications based on AWS Well-Architected Framework best practices. “Cedrus is proud to be an AWS Well-Architected Partner, building upon our history of helping AWS customers innovate and modernize in a secure and scalable manner,” said Mike Chadwick, SVP of Business Development and Sales at Cedrus. “The AWS Well-Architected program ensures that our customers’ AWS environments follow best practices and deliver agility, reliability, security, and rapid innovation.” AWS is enabling scalable, flexible, and cost-effective solutions from startups to global enterprises. To support the seamless integration and deployment of these solutions, AWS established the AWS Well-Architected Partner Program to help customers identify APN Consulting Partners with deep expertise in optimizing workloads and mitigating risks in their workloads. Leveraging the principles of the AWS Well-Architected Framework, the Cedrus team has been helping customers gain visibility into their AWS environments and develop pragmatic, prioritized action plans. Cedrus boasts deep expertise in helping enterprises with modernization of complex workloads. The AWS Well-Architected Framework has proven to be a critical pillar in supporting growing enterprise adoption of governance and policy as code to drive ongoing security posture and automated compliance with corporate standards. AWS customers can contact Cedrus for a walk-through of a Well Architected Review and how Cedrus can help build a secure AWS plan and roadmap. Email: About Cedrus - Cedrus designs, develops, and implements modern cloud applications that drive digital transformation at global brands. We are a trusted advisor for design thinking, innovation and modernization founded on expertise in cloud security, cloud native application development, cognitive business automation and systems integration.

    • Cedrus launches new service on Professional Services in AWS Marketplace

      [December 3, 2020]– Cedrus, a highly sought-after digital transformation solutions provider and AWS Consulting Partner, announced today that it is participating in the launch of Professional Services in AWS Marketplace. Amazon Web Services (AWS) customers can now find and purchase cloud development, cloud security, advisory and process automation services from Cedrus in AWS Marketplace, a curated digital catalog of software, data, and services that makes it easy to find, test, buy, and deploy software and data products that run on AWS. As a participant in the launch, Cedrus is one of the first AWS Consulting Partners to quote and contract services in AWS Marketplace to help customers design, implement, optimize, secure and manage their software on AWS. With professional services from Cedrus available in AWS Marketplace, customers have a simplified way to purchase and be billed for both software and services in a centralized place. Customers can further streamline their purchase of professional services and software with standard contract terms to simplify and accelerate procurement cycles. . “Cedrus is proud to support professional services in AWS Marketplace,” said Mike Chadwick, SVP of Business Development and Sales. “Our team is dedicated to helping companies find the complete cloud solutions they need to innovate and migrate to the cloud. Now, our customers can access cloud software solutions and our associated services to help them implement and manage their workloads on AWS from one centralized location.” Available upon launch of the Professional Services Marketplace in AWS, is the Cedrus Cloud Architecture and Security Review. The Cedrus Cloud Architecture and Security Review provides in-depth investigation, security risk analysis and review of AWS architectures, workloads, and governance. Using a Cedrus developed methodology and toolset that is more comprehensive than Well-Architected Frameworks and reviews, expert cloud security engineers correlate, and cross validate hundreds of variables with events, policies, practices, and system configurations to determine your at-risk status. This unique approach identifies liabilities, risks, and opportunities to improve your security posture that other assessments miss. AWS customers can contact Cedrus for a walk-through of an actual Cedrus Cloud Architecture and Security Review and compare the gaps their internal assessments may be missing. Email: About Cedrus - Cedrus designs, develops, and implements modern cloud applications that drive digital transformation at global brands. We are a trusted advisor for design thinking, innovation and modernization founded on expertise in cloud security, cloud native application development, cognitive business automation and systems integration.

    • Cleaner Microservice Orchestration With Zeebe+Lambda

      Brian McCann, Software Engineer In this post I’ll talk about Zeebe. Zeebe is a source available workflow engine that helps you define, orchestrate, and monitor business processes across microservices. I’ll show you how to quickly get a full application that leverages Zeebe and Lambda running on AWS. I’m piggybacking off a post by the company’s co-founder in which he showed how you can use Zeebe with Lambda. You may want to start with that one first for a general overview of Zeebe and how it fits in with Serverless, then if you’re interested in quickly getting all the components running on AWS this post will show you how. If you embrace AWS Lambda or are considering adopting it you may see Lambda as an alternative to Kubernetes and prefer the simplicity, reliability, and out of the box scaling that the Serverless way offers. I was motivated to write this for that type of developer. For Zeebe to work we need something running all the time so we can’t be fully “serverless”. My concession is to use ECS to bridge the gap. ECS is a simpler and cheaper alternative to Kubernetes when you’re getting started with containers. If you are a serverless first developer you or your organization might not want to take on the overhead of running and learning k8s if almost all your workloads work fine on Lambda anyway. Zeebe is a super powerful tool that allows you to compose your Lambda functions to build arbitrarily complex stateful applications. Today I’ll show how to get up and running quick with Zeebe and Lambda using ECS. This is what we’ll make Use Case? In case you don’t know about Zeebe I’ll try to describe what it does by describing a use case. A little while ago I was working on a backend that would allow customers to put a down payment on a vehicle then go pick it up at a dealership. The whole process wasn’t too complicated but did involve 5–6 discrete steps involving external API calls. Any of those steps had a number of potential failure paths and based on the outcome of each step you would want to take a different action. On top of that there are different types of errors. There are errors due to conditions in the physical world like a customer putting their address in wrong and there are technical errors like network outages or a bug in the code. You can imagine how the number of scenarios grows exponentially each time you add a step. General purpose programming languages on their own are great at a lot of things, Orchestrating a complicated sequence of steps is not one of them. Using event driven architecture can help us manage emerging complexity by separating business logic into individual microservices whose isolated behavior is simpler to reason about. What we lose is end to end visibility of the business process, so that debugging is a challenge and refactors are scary. This is where a tool like Zeebe, or its predecessor Camunda can help. These tools let us represent our processes as diagrams that are executable. Here is an example: One of the main advantages is that our business logic is now organized into manageable and isolated components. In addition, and in my opinion most importantly, this strategy separates the concern of Orchestration from everything else. This allows us to write functional style microservice components that are easy to read and refactor. All of our orchestration is managed by a dependable and tested framework, and the orchestration logic is cleanly separated as opposed to peppered throughout our microservices (as tends to happen). The boxes with gears are “service tasks” which means they represent pieces of code external to Zeebe that execute. The process engine (Zeebe) is responsible for executing the instructions and will invoke the code we’ve written where specified. In today’s example the service tasks (little boxes with gears ) will be implemented as Lambda functions. There are a lot of other powerful features exposed by BPMN (business process modeling notation), the ones pictured above are just a few. We need a way for Zeebe to trigger the Lambda functions because Lambda functions by design are dormant until you trigger them. We will use the code provided by the zeebe-lambda-worker to create a link between the orchestrator (Zeebe) and the business logic (Lamba). The worker will listen for events on the Zeebe broker, pick up work tasks as they come in, and forward the payload to Lambda. The original post covers how all this works. Here is what I’m adding How to spin up an ECS cluster and run the zeebe-lambda-worker on it How to use an IAM role for authorization instead of AWS credentials Here are the steps involved in this walkthrough: 1. Get set up with Camunda Cloud Sign up for a Free Camunda Cloud trial account Launch a Zeebe instance 2. Use the Serverless Framework to deploy several Lambda functions and an IAM role 3. Get set up on ECS Create an ECS cluster using a setup shell script Deploy the zeebe-lambda-worker to ECS 4. Test that everything works end to end Sign up for Camunda Cloud Camunda and Zeebe are the same company. Zeebe is their newer product and Camunda Cloud is their managed cloud offering which happens to run on the newer Zeebe engine. It’s confusing, I know, probably has something to do with marketing as Camunda is an established and fairly well known brand. Getting set up with a development Zeebe instance is fairly straightforward. This post from the zeebe blog walks you through the steps. The whole thing is a good read but you can skip everything after the create a client part if you just want to get up and running. We’ll need the broker address information and the client information later. Once we’re set up with a free Zeebe instance we can deploy the Serverless framework project. Deploy the serverless project prerequisite: You need to have an AWS account + IAM user set up with admin privileges. This is a great guide if you need help. clone the repo cd into this directory trip-booking-saga-serverless/functions/aws In the serverless.yml file update the region property If you’d like to deploy to a region other than us-east-1. I have made barely any changes to this from the original original forked repository. I removed the http event triggers from the functions since we won’t need them for this. This will make the project deploy and tear down faster since there are no API gateway resources. I also defined an IAM role that will give our zeebe-lambda-worker (which we have yet to deploy) permission to invoke the Lambda functions. The policy portion of the role we’ll give to the ECS lambda-worker Run the command sls deploy -v to deploy the Lambda functions (the -v gives you verbose output). Connecting Lambda + Zeebe with ECS The last step to get our demo application working end to end is to deploy the zeebe-lambda-worker. The source code can be found here. I also forked this from Zeebe and made a small change which was to add support for IAM role authorization. Since our ECS task will assume a role that gives it permission to invoke the Lambda functions it needs to, we do not need to supply AWS credentials to the worker code. I added an if / else statement so that a role will be used if no AWS credentials are supplied. This works because the AWS sdk sources credentials hierarchically. The role referred to in this snippet is the one we created earlier when we deployed the Serverless framework project. If you prefer to use accessKey/secretKey make sure those keys are not the same keys you use as an admin user to work with AWS. You should create a role or user with credentials that allow the least permission possible. In this case we only need permission to invoke a few specific Lambda functions. I have already packaged the zeebe-worker as a Docker image and pushed to a public repo. The ECS setup which we will get to in a moment will pull this image. If you want you can modify the worker source code and/or build the image yourself and publish to your own repository. You’ll need to package it as a .jar first as it is Java code. Prerequisite: ecs-cli installed on your machine. You can get it with aws binary or homebrew If you run into issues at any point look at the AWS walkthrough for reference. I mostly followed the steps outlined there to do this with a few minor modifications. I have chosen to use a launch type of EC2. Fill in some configuration To make it easy to configure your ECS cluster I’ve included some configuration template files, all of which have the word “SAMPLE” in the file name. To use them, cd into zeebe-event-adapter/ in the trip-booking-saga repo. Then copy all the files with the word SAMPLE in front and save them with “SAMPLE” removed from the file name. This will cause them to be ignored by git. I’ve configured the .gitignore to ignore these files so that you or I don’t accidentally commit sensitive credentials to source control. Next, populate the values in each file as outlined below. (file) aws.env AWS_REGION= --- (file) Camunda.env ZEEBE_CLIENT_CLOUD_CLUSTERID= ZEEBE_CLIENT_CLOUD_CLIENTID= ZEEBE_CLIENT_CLOUD_CLIENTSECRET= --- (file) ecs-params.yml ... # modify this line task_role_arn: arn:aws:iam:::role/zeebe-lambda-worker-role ... The values we supply in Camunda.env will be used by the zeebe-lambda-worker to connect to the Camunda Cloud Zeebe instance we created in the first step. Once we’ve filled in the values in each of these files we’re ready to deploy. I’ve combined all the steps into one bash script so everything can be deployed with one command. Just run the script and supply your region as the only argument. i.e. bash us-east-1 If you run into problems at any step you may want to try running the commands in the script one by one manually, or refer back to the AWS tutorial. # note you may get this warning INFO[0010] (service aws) was unable to place a task because no container instance met all of its requirements. Don’t get impatient and kill the process, this just means your infra isn’t quite ready yet, it should resolve on its own. If you are used to working with Kubernetes the ECS terms will be confusing. An ECS service is not the same as K8s service at all and has nothing to do with networking. Instead in ECS a service just defines that you want to keep a “task” (which is basically a container with some config attached) running. It’s the same idea as a service you’d set up on a Linux server. Test that it works *disclaimer The main purpose of this post is to show how to easily deploy the zeebe-lamba-connector to work with Lambda functions so I won’t cover Zeebe usage much. If you want to learn more about Zeebe check out Bernd Rücker’s posts or try the zeebe quickstart. Probably the simplest way to deploy and start the workflow is with the Zeebe Modeler tool which you can download here . You can also use the command line tool zbctl. Once you have the modeler downloaded, just open the trip-booking.bpmn file (in zeebe/aws directory) in the zeebe modeler. Use the upload and play buttons to upload the workflow to the cluster and start an instance of the process. If the process instance worked successfully end to end you will see the completed instance in the operate console. If we navigate to ECS, select the service we’ve deployed and click on logs, we can see the successful results from the Lambda functions being passed back and forth through the zeebe-lambda-worker. Also if we navigate to the Lambda console, select one of the Lambdas involved in our workflow then select monitoring → view logs in cloudWatch, we can see the logs of the Lambda function itself. Cleaning up ECS resources when you don’t want them anymore take down the service ecs-cli compose service rm — cluster-config zb-cfg remove the whole cluster ecs-cli down — force — cluster-config zb-cfg Closing thoughts I am curious to hear what others think about pairing Zeebe with Lambda. Does the combination make sense? What would you do differently? Also for anyone who uses or has used step functions I am curious to hear how this solution compares. I had not used ECS much before this and I was pleasantly surprised by how easy it was to provision and use. It seems like they’ve added a lot of features since the last time I looked at it to try to keep pace with Kubernetes. I also like how they use a docker-compose file and docker like commands so you can work with your containers in the cloud more or less the same way you would locally. My one big concern and hesitation on getting good at ECS is that its clearly not the industry standard. Practically as engineers it just makes way more sense to use what everyone else is using because thats what everyone already knows. I think Zeebe is a very promising new product, I also think they have their work cut out for them because there are a lot of competitors in this space. Some popular tools that fill the same Niche are Netflix’s Conductor and AWS’s own Step Functions. They face competition not just from competitor frameworks but also homespun orchestration solutions using event buses and other lower level orchestration/choreography tools. I think that a lot of orgs and developers don’t even realize that there is a tool that can help them glue together or orchestrate microservices. In a lot of cases people tend to write this code themselves. In many cases it is a conscious decision because they feel that adding in another Library just creates additional complexity, makes their app harder to understand for new developers, or perhaps even limits what they can do. I totally get that concern as I’ve had these problems myself. For my personal development and collaboration style I think Zeebe makes a lot of sense for a broad range of tech problems. I hear about a lot of people reaching for Kafka to achieve EDA. I have nothing against Kafka and I think it is a technically impressive piece of engineering. An experienced dev can probably get up and running with it in a day but they definitely won’t be using it optimally or even getting benefits from it for a long time because it is so complicated with tons of use case specific config required. Kafka is more low level than Zeebe and therefore applies to a broader range of use cases. However I think that if you are just using Kafka as an event bus to drive a collection of choreographed microservices, Zeebe may offer a simpler and actually more powerful solution. With Kafka things like event replay, retry strategies, and monitoring solutions at a business process level, are capabilities we need to build ourselves. Zeebe is appealing to me because they’ve found a way to generalize these needs. This allows us as developers to simply use their API to endow our apps with these advanced features and ultimately solve a business problem.

    View All
    Pages (21)
    • JOBS | Cedrus Digital

      Line separator JOIN THE TEAM Want to join our stellar team of hard-working, talented, creative people? Drop us a line if you think you'd be a good fit for any of our job openings. COME WORK WITH US ! We are always looking for bright, driven individuals to join our slightly unconventional team. Are you looking to grow and learn in your career? Not afraid to speak your mind when you create? Want to be part of a team of unlike-minded peers? You may just be a great fit! You'll get amazing experience We have numerous clients in diverse lines of business, with expansive projects that will let you flex and expand your expertise. We will foster your growth Be part of an awesome team Our team has years of mentorship experience. We keep our team members up-to-date with the latest technology, providing resources for learning, a team learning culture, and supporting the acquisition of certifications. We're an unusual mix of people with diverse experience and a can-do attitude. Our team is motivated, hungry to learn, and eager to contribute and take ownership of their work. Our office space rocks Cedrus is located in the heart of Manhattan with easy bike access, endless coffee, and community collaboration and gatherings. You will have remote options Team members have the autonomy to work remotely as needed once they are up to speed with their team's needs and rhythms. WE'RE HIRING

    • Cedrus Digital | Customized Digital Transformation

      Line separator DIGITAL TRANSFORMATION SOLUTIONS DONE RIGHT Your company is unique; your technology solutions should be too. Our expert consultants advise and aim to tailor our solutions to your specific business needs with unprecedented speed and agility. Why trust your innovation to anyone else? WHAT WE DO FEATURED PARTNERSHIPS OUR VISION To deliver our customers innovative solutions with unparalleled levels of functionality and sophistication, bridging the present into the future, while bringing unprecedented operational efficiencies into their business. WHO WE ARE 82 % Repeat Customers 164 % Customer base growth over the last 4 years 44 % CAGR for the past 3 years About Cedrus We are a young, imaginative, diverse company, deeply rooted in successfully solving large business problems for the past 25 years. Our employees, partners, and customers share our zeal for excellence. Learn more about what makes us special. MEET CEDRUS Our Expertise We tame cutting-edge technologies to fit your business. Our extensive certifications, internal investments in assets and IP, and our experience from hundreds of transformational projects inform our wisdom as we take on new challenges. OUR EXPERTISE HOW WE'RE DIFFERENT We expertly guide you through discovery and design, architecture and development, and production and support, with an approach perfectly tailored to your unique business needs. Realizing your business' potential has never been easier! Learn about our offerings at no commitment, risk, or cost. WHAT WE DO See us in action! Get to know our work through some real-life examples. Take a look at some use cases, demos, and solutions that others are already implementing . USE CASES Grow with us! WE ARE HIRING! Want to be part of a dynamic, creative team? Want to join a company that will invest in you? Learn more about joining our team. JOIN US OUR PARTNERSHIPS Our close partnerships with some of the industry's top performers will give you the best experience in using their groundbreaking, industry-defining tools and platforms. By keeping an open mind, a scientific curiosity, and an objective outlook, we accommodate and adapt our recommendations to the context of your business. LEARN MORE WHAT WE'RE UP TO NOW Cleaner Microservice Orchestration With Zeebe+Lambda 14 Write a comment Automatic Text Summarization: Demystified 8 Write a comment AWS Blog: FADEL Reduces API Generation from Days to 30 Minutes on AWS Read about our success with Fadel on the AWS blog here: 3 Write a comment View More WHAT PEOPLE SAY Media and Entertainment Software Provider We were impressed with Cedrus' ability and assets to support us during our Cloud migration. Cedrus is not a typical systems integrator- they understand the underlying business challenge and help resolve it through cutting edge technology practices. Their unparalleled expertise in implementing and deploying APIs/microservices to the Cloud enabled us to quickly and smoothly transition our software offerings to AWS. READY TO GET STARTED ? Get in touch with us! We're thrilled to answer your questions and help you define a vision. Contact Us

    • Who We Are

      OUR TEAM In the Era of Digital Transformation, where a lot of so-called strategic players talk the talk, we walk the walk. We think strategically but execute tactically. One step at a time, we will guide you through your Digital Transformation journey while helping you build skills internally. Our assets and IP, strategic partnerships, and long experience servicing some of the world’s largest firms ensure your success. OUR MISSION Assist our customers on their path to digital transformation. Bring them advice, expertise, and experience to allow them to securely expand their business and streamline their processes. OUR CULTURE Despite Cedrus’ relatively young age, our executive and senior team have been working together, solving large scale problems at some of the world’s largest companies, for more than 25 years. Our DNA and culture are deeply rooted in an uncompromising value system: fairness and ethics, inside and out. While being recognized for their industry and technology vision and leadership, our senior executives and senior managers remain rooted in the realities of projects and customers’ needs. This “shot of reality” is key to evolve our offerings, practices, investments and partnerships. ​ OUR MORAL COMPASS ​ Be on their side. Maximize the value to cost ratio. Deliver to exceed expectations. It's no surprise why more than 2/3 of our business is with repeat customers. With our customers: Fair chance for all. Merit-based place of work, with accountability and equal opportunity for growth. Our people are held to the highest ethics and standards, and we only hire people that respect and fight for such values. Cedrus is an Active Equal Opportunity Employer, with the mission to prove that business and social responsibilities can co-exist and lead to great successes. We reject and fight against any form of discrimination and hatred and are leading every day by example to eliminate all these forms of inequalities in society. With our people: MEET THE TEAM Nicolas Jabbour CEO Entrepreneur and Technology veteran. Leads the vision at Cedrus. At the service of our customers and our teams. Mike Chadwick SVP of Business Development and Sales Responsible for Sales and Partner Strategy. Believes in the union of technical skills and business value through a design-based approach. Passionate about delivering the right solution and implementing it the right way. Ashraf Souleiman Cloud Native Lead Cloud Practice Lead. Helps organizations implement their digital transformation vision and optimize their end-to-end digital experiences. Hanna Aljaliss Cognitive Automation Lead Focuses on developing business accelerators and innovations using process automation and artificial intelligence to derive business process improvement and operational efficiency. Kyle Watson Security Lead Guides and advances the cloud security consulting team. Ensures quality in delivery and customer success. Sets investment priorities in security tech. Charles Allen Human Resources To foster positive values and culture is key. A focused HR leader that helps culminate the team at Cedrus towards a forward movement. Matt Hejnas Principal Architect Cloud Integration Competency Lead with deep experience architecting, designing, and delivering integration solutions on and off prem, with APIs and Streams for our customers. Chris Brause UX Competency Lead Leading a team of innately curious designers who define the what, why, and how of usable, beautiful products. Paul Ilechko Netskope Consulting Services Lead Provides technical leadership and guidance to ensure successful project outcomes for our Netskope customers, working closely with our technology partners. Chris Dougherty Practice Solution Architect/SE Guides customers on selecting and implementing appropriate cloud security solutions to solve their business and regulatory needs. Mohamed Maher Architecture & Middleware Solutions Lead Solutions Architect with over 20 years hands-on experience on wide list of technologies. Expertise in designing and delivering solution around Business process automation and process improvements Ez Nadar AI Solutions Lead Head of AI Solutions. Focuses on transforming businesses into AI enterprises through the development & integration of conversational AI, NLP, and predictive analytics into their business workflow.

    View All


search icon.png

530 5th Ave, Suite 804

New York City, NY 10036

  • Facebook
  • Instagram
  • LinkedIn
  • Twitter
  • YouTube

© 2020 by Cedrus Digital.